Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dd135fc63415f6605445679eb86fbd6f3c68eebeeea8a749f4fe52860c63d16

Tx prefix hash: 63e03844bbb77c8c0bbee02958cfedfaa7d6fb603306e9382df5c6a7548802a2
Tx public key: 0f3aed4198bffcc3c73e5412678fbb3a0d569ccf3455a0e0ac2ae3e34b810744
Timestamp: 1704176190 Timestamp [UCT]: 2024-01-02 06:16:30 Age [y:d:h:m:s]: 01:097:23:33:30
Block: 926360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331135 RingCT/type: yes/0
Extra: 010f3aed4198bffcc3c73e5412678fbb3a0d569ccf3455a0e0ac2ae3e34b8107440211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d5afdabe355ff5d640d0ec87ecae8f0fe862e0898771515cba32b5ac738706f 0.600000000000 1384142 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": 926370, "vin": [ { "gen": { "height": 926360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d5afdabe355ff5d640d0ec87ecae8f0fe862e0898771515cba32b5ac738706f" } } ], "extra": [ 1, 15, 58, 237, 65, 152, 191, 252, 195, 199, 62, 84, 18, 103, 143, 187, 58, 13, 86, 156, 207, 52, 85, 160, 224, 172, 42, 227, 227, 75, 129, 7, 68, 2, 17, 0, 0, 0, 3, 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