Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0e4a36364af8ec5aa01b1c907b0af8d63217fa40b5ac84f461ad81a3c45598c

Tx prefix hash: 08bd1750f7a2c0c47256520a751c3e99e3bc0ded25f684cf08575e6f54e01d2e
Tx public key: b12c168978258d3ca960e14918bd41313abf0831b6b419fba72de12b00705298
Timestamp: 1643894356 Timestamp [UCT]: 2022-02-03 13:19:16 Age [y:d:h:m:s]: 03:006:10:02:58
Block: 431361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 783750 RingCT/type: yes/0
Extra: 01b12c168978258d3ca960e14918bd41313abf0831b6b419fba72de12b00705298021100000008cb8520c2000000000000000000

1 output(s) for total of 22.841375141000 dcy

stealth address amount amount idx
00: 974c2aa429d527e8cb1cc0743a49bf65d95976447893b9489a0d46d972a90b4a 22.841375141000 841539 of 0

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": 431371, "vin": [ { "gen": { "height": 431361 } } ], "vout": [ { "amount": 22841375141, "target": { "key": "974c2aa429d527e8cb1cc0743a49bf65d95976447893b9489a0d46d972a90b4a" } } ], "extra": [ 1, 177, 44, 22, 137, 120, 37, 141, 60, 169, 96, 225, 73, 24, 189, 65, 49, 58, 191, 8, 49, 182, 180, 25, 251, 167, 45, 225, 43, 0, 112, 82, 152, 2, 17, 0, 0, 0, 8, 203, 133, 32, 194, 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