Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a944e30899c0a074252f377f316baabaa2691d510a26d7af6fa6484e4714f7d

Tx prefix hash: d4b8dfc0dfa9721e0ecca2d20334af638fca9a102e43c8df8fde9174ac44a160
Tx public key: 0547c9e362b85609023bfc68da4bf8e6c2617e7bcedc15e549553a1c96c26ab4
Timestamp: 1624609802 Timestamp [UCT]: 2021-06-25 08:30:02 Age [y:d:h:m:s]: 03:230:21:25:05
Block: 284001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 932018 RingCT/type: yes/0
Extra: 010547c9e362b85609023bfc68da4bf8e6c2617e7bcedc15e549553a1c96c26ab40211000000160f4c30de000000000000000000

1 output(s) for total of 70.307617042000 dcy

stealth address amount amount idx
00: 1dbac740b7d9f51bec1a19addd1479691785949c547e9577b4973af1d720083e 70.307617042000 594634 of 0

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": 284011, "vin": [ { "gen": { "height": 284001 } } ], "vout": [ { "amount": 70307617042, "target": { "key": "1dbac740b7d9f51bec1a19addd1479691785949c547e9577b4973af1d720083e" } } ], "extra": [ 1, 5, 71, 201, 227, 98, 184, 86, 9, 2, 59, 252, 104, 218, 75, 248, 230, 194, 97, 126, 123, 206, 220, 21, 229, 73, 85, 58, 28, 150, 194, 106, 180, 2, 17, 0, 0, 0, 22, 15, 76, 48, 222, 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