Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c6207b8e028a27ce1398acd2a9d1e50d94334a5385f25476905f7f8aace5c1d

Tx prefix hash: c0006551c32d41ed0ba677be4e166dfea19b0693d95f9b7b03730341aba31e64
Tx public key: a6d2adb0984a9957173f77c7b73b66a8e501dac2dc04e27982495488f67bb12e
Timestamp: 1713626493 Timestamp [UCT]: 2024-04-20 15:21:33 Age [y:d:h:m:s]: 00:352:07:17:50
Block: 1004697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251861 RingCT/type: yes/0
Extra: 01a6d2adb0984a9957173f77c7b73b66a8e501dac2dc04e27982495488f67bb12e0211000000100011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5a23836776a3858d54a8362700957ddcd9dc85b5304aa9c5d58e1113e0540a3 0.600000000000 1465269 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": 1004707, "vin": [ { "gen": { "height": 1004697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5a23836776a3858d54a8362700957ddcd9dc85b5304aa9c5d58e1113e0540a3" } } ], "extra": [ 1, 166, 210, 173, 176, 152, 74, 153, 87, 23, 63, 119, 199, 183, 59, 102, 168, 229, 1, 218, 194, 220, 4, 226, 121, 130, 73, 84, 136, 246, 123, 177, 46, 2, 17, 0, 0, 0, 16, 0, 17, 5, 91, 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