Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2814fbb678629165e46dcb8b361841fc43d0c9e9f59d5ee20177fe8ae1823d5c

Tx prefix hash: 2bf6f061a77378d72b6354249da174f5792d530d29b9d37eb3fe42e940c5fa5b
Tx public key: 64896fad6c04528904dd29442ca162e879b5e0a35b5415f60e09b5d84a6770d2
Timestamp: 1710873474 Timestamp [UCT]: 2024-03-19 18:37:54 Age [y:d:h:m:s]: 01:233:22:50:02
Block: 981914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 425879 RingCT/type: yes/0
Extra: 0164896fad6c04528904dd29442ca162e879b5e0a35b5415f60e09b5d84a6770d20211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2c09beec2d88ab053016cafe691b2eb20c2ae393cb3c5e71ed9058f48ce4b14 0.600000000000 1442017 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": 981924, "vin": [ { "gen": { "height": 981914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2c09beec2d88ab053016cafe691b2eb20c2ae393cb3c5e71ed9058f48ce4b14" } } ], "extra": [ 1, 100, 137, 111, 173, 108, 4, 82, 137, 4, 221, 41, 68, 44, 161, 98, 232, 121, 181, 224, 163, 91, 84, 21, 246, 14, 9, 181, 216, 74, 103, 112, 210, 2, 17, 0, 0, 0, 2, 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