Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca353f22da9fe859a8eaa3e8703f76a7ec8a302b1eacad297bcda59fa64370df

Tx prefix hash: ae26597575c5dcb3754888c607db6337187523f6e909995f829af6622ec61d5b
Tx public key: 745afc47fbe56826a93705d177473a6b2bdd5378f9f32fa4a7b51f814c919b38
Timestamp: 1729735079 Timestamp [UCT]: 2024-10-24 01:57:59 Age [y:d:h:m:s]: 00:193:16:08:10
Block: 1138230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138236 RingCT/type: yes/0
Extra: 01745afc47fbe56826a93705d177473a6b2bdd5378f9f32fa4a7b51f814c919b380211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 271641c05c14bc435c6015a768e4a7eaae37def678e9e7741274338a35d1db7e 0.600000000000 1621855 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": 1138240, "vin": [ { "gen": { "height": 1138230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "271641c05c14bc435c6015a768e4a7eaae37def678e9e7741274338a35d1db7e" } } ], "extra": [ 1, 116, 90, 252, 71, 251, 229, 104, 38, 169, 55, 5, 209, 119, 71, 58, 107, 43, 221, 83, 120, 249, 243, 47, 164, 167, 181, 31, 129, 76, 145, 155, 56, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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