Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f6b5eb4bb699870ca58391b4dae3d1d6e690731721f574d94eddcdc93534941

Tx prefix hash: 3a67dcb216b0d2b29ad1be66a7d818b6cbaf49fe29f75df034000869bbebb0c4
Tx public key: bdd9dc1b056ad8da50cf279774072bda7531f47c8195126316f7f9d87ca716b3
Timestamp: 1751273819 Timestamp [UCT]: 2025-06-30 08:56:59 Age [y:d:h:m:s]: 00:139:01:45:34
Block: 1315734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97588 RingCT/type: yes/0
Extra: 01bdd9dc1b056ad8da50cf279774072bda7531f47c8195126316f7f9d87ca716b30211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0abf4e3ea99cc37ba6fa3e9fe39a77abebc63d85e5482c890f8539687b3f019 0.600000000000 1803389 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": 1315744, "vin": [ { "gen": { "height": 1315734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0abf4e3ea99cc37ba6fa3e9fe39a77abebc63d85e5482c890f8539687b3f019" } } ], "extra": [ 1, 189, 217, 220, 27, 5, 106, 216, 218, 80, 207, 39, 151, 116, 7, 43, 218, 117, 49, 244, 124, 129, 149, 18, 99, 22, 247, 249, 216, 124, 167, 22, 179, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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