Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4b85feb1ab2f2dd53b444b95235d9f61e185a65edade698d1d233c204e5b8eb

Tx prefix hash: 5e2264afd0654398082f8ecf206d9dd8333b613b48268cfb035d34e72011f219
Tx public key: 82655ea58c7610541a344251e86a86d80a2da5fc5c32790a0a068defa3f3dd7c
Timestamp: 1731851941 Timestamp [UCT]: 2024-11-17 13:59:01 Age [y:d:h:m:s]: 00:186:23:59:24
Block: 1155717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133508 RingCT/type: yes/0
Extra: 0182655ea58c7610541a344251e86a86d80a2da5fc5c32790a0a068defa3f3dd7c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81a9e819b725f320f0e488bb09fe6cdb63f7d026c8ec2a148bfd042f390c2ea6 0.600000000000 1641334 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": 1155727, "vin": [ { "gen": { "height": 1155717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81a9e819b725f320f0e488bb09fe6cdb63f7d026c8ec2a148bfd042f390c2ea6" } } ], "extra": [ 1, 130, 101, 94, 165, 140, 118, 16, 84, 26, 52, 66, 81, 232, 106, 134, 216, 10, 45, 165, 252, 92, 50, 121, 10, 10, 6, 141, 239, 163, 243, 221, 124, 2, 17, 0, 0, 0, 2, 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