Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b12f72d40717e0fdbc4ddfd4fa43749683c6eaa0104ced4f5fc0b257b01540e0

Tx prefix hash: b0d42a26077ab42c84438b004e22b96702d41425716abd619d67ccb75041b719
Tx public key: 3fd02d445fc95314c05d0e7b4a5d11e8fc53016309202f82a4d1870179b6223d
Timestamp: 1750195220 Timestamp [UCT]: 2025-06-17 21:20:20 Age [y:d:h:m:s]: 00:155:10:34:29
Block: 1307199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108901 RingCT/type: yes/0
Extra: 013fd02d445fc95314c05d0e7b4a5d11e8fc53016309202f82a4d1870179b6223d021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 620dbf36da74bccd1b55adab71d86fb75e00de801fd8879b3a608980866bd1d9 0.600000000000 1794808 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": 1307209, "vin": [ { "gen": { "height": 1307199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "620dbf36da74bccd1b55adab71d86fb75e00de801fd8879b3a608980866bd1d9" } } ], "extra": [ 1, 63, 208, 45, 68, 95, 201, 83, 20, 192, 93, 14, 123, 74, 93, 17, 232, 252, 83, 1, 99, 9, 32, 47, 130, 164, 209, 135, 1, 121, 182, 34, 61, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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