Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a0894041b391e6e5a468e60fc11e373869f5646e5e186fa3810202957f69aea

Tx prefix hash: d505a2ddcb928cdd339683bc43e81caae09e14f057e6708ddbfbcd3cc32689ff
Tx public key: 33a8e3fa3e57e60c31b591c22c64907801253ce091f1342342b1fdc6cf0de158
Timestamp: 1711327133 Timestamp [UCT]: 2024-03-25 00:38:53 Age [y:d:h:m:s]: 01:041:11:39:33
Block: 985673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290621 RingCT/type: yes/0
Extra: 0133a8e3fa3e57e60c31b591c22c64907801253ce091f1342342b1fdc6cf0de158021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9a304ab024af3b30cc6cc94c83b2eea711f8213c805f62bd674d9cf83b26394 0.600000000000 1445890 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": 985683, "vin": [ { "gen": { "height": 985673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9a304ab024af3b30cc6cc94c83b2eea711f8213c805f62bd674d9cf83b26394" } } ], "extra": [ 1, 51, 168, 227, 250, 62, 87, 230, 12, 49, 181, 145, 194, 44, 100, 144, 120, 1, 37, 60, 224, 145, 241, 52, 35, 66, 177, 253, 198, 207, 13, 225, 88, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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