Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 82ce565696be1f448b061b0d0d8219132bf2b7cdad71cb4a61693ba390af07c1

Tx prefix hash: b637a4b691d6032e76c0dd5fd059b432aea580a334e5630013cc0d8f093b8f3c
Tx public key: dbe0ac285e65e0e8bb454f7a76049f15938b2bfc8d3f427bc46b7c48637b56a5
Timestamp: 1750940649 Timestamp [UCT]: 2025-06-26 12:24:09 Age [y:d:h:m:s]: 00:144:20:52:53
Block: 1313178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101536 RingCT/type: yes/0
Extra: 01dbe0ac285e65e0e8bb454f7a76049f15938b2bfc8d3f427bc46b7c48637b56a5021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27aa664fb1578577911b421913bd194d04073ffed18814f03895b24ba268f278 0.600000000000 1800817 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1313188, "vin": [ { "gen": { "height": 1313178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27aa664fb1578577911b421913bd194d04073ffed18814f03895b24ba268f278" } } ], "extra": [ 1, 219, 224, 172, 40, 94, 101, 224, 232, 187, 69, 79, 122, 118, 4, 159, 21, 147, 139, 43, 252, 141, 63, 66, 123, 196, 107, 124, 72, 99, 123, 86, 165, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8