Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 216cd1020b2a882efa711116710300784f583eeee42e85a1e48315e8db15354b

Tx prefix hash: 0dd2b41c8d927eee05ac90202a5a61b8f875945d02ecff23e895eeda947911a4
Tx public key: 6fba861e3a3ea84541dd6d8281b8cb4856ad8ae91b86a8dd8daa699973ce5840
Timestamp: 1751603801 Timestamp [UCT]: 2025-07-04 04:36:41 Age [y:d:h:m:s]: 00:134:21:51:29
Block: 1318391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94688 RingCT/type: yes/0
Extra: 016fba861e3a3ea84541dd6d8281b8cb4856ad8ae91b86a8dd8daa699973ce584002110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e38d575c7549e176074a4b9f01d847b51d82e5e56adc72bfe4ed5f10967c266b 0.600000000000 1806070 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": 1318401, "vin": [ { "gen": { "height": 1318391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e38d575c7549e176074a4b9f01d847b51d82e5e56adc72bfe4ed5f10967c266b" } } ], "extra": [ 1, 111, 186, 134, 30, 58, 62, 168, 69, 65, 221, 109, 130, 129, 184, 203, 72, 86, 173, 138, 233, 27, 134, 168, 221, 141, 170, 105, 153, 115, 206, 88, 64, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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