Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d03243f46cfd3738f5250a1eda30954ad629851d14d0ce239da216b4e9f88ce7

Tx prefix hash: 34d92f423911bf4e5324ec1de43f643da56a1347a57c398c26e6c9da9990beb8
Tx public key: 0f7ff2927ab8b544a8f3c7deec5aa0efa58a3591620da40608e3421d37958759
Timestamp: 1704260942 Timestamp [UCT]: 2024-01-03 05:49:02 Age [y:d:h:m:s]: 01:305:19:27:16
Block: 927061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477392 RingCT/type: yes/0
Extra: 010f7ff2927ab8b544a8f3c7deec5aa0efa58a3591620da40608e3421d379587590211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e0f7c3516f3be84ec5891d4659faf5cab6693af8b4afbb9491b6ad053d325b0 0.600000000000 1384861 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": 927071, "vin": [ { "gen": { "height": 927061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e0f7c3516f3be84ec5891d4659faf5cab6693af8b4afbb9491b6ad053d325b0" } } ], "extra": [ 1, 15, 127, 242, 146, 122, 184, 181, 68, 168, 243, 199, 222, 236, 90, 160, 239, 165, 138, 53, 145, 98, 13, 164, 6, 8, 227, 66, 29, 55, 149, 135, 89, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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