Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6a588402d839008f34bbabd2c0fb3011f0355f58bdc3bbba17d1b871237e228

Tx prefix hash: 566bb099f33686278202b8b0c3e0d58859c313ff31dfb0d133d166a984ed6c7a
Tx public key: 216c242d0fd265296d3da2aa2944ff5b436d94b00186318dc50c4a0e5a18105f
Timestamp: 1704915111 Timestamp [UCT]: 2024-01-10 19:31:51 Age [y:d:h:m:s]: 01:071:11:18:21
Block: 932483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312177 RingCT/type: yes/0
Extra: 01216c242d0fd265296d3da2aa2944ff5b436d94b00186318dc50c4a0e5a18105f02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5a10dba1cde32a4862e73914e9cda898c86c134630f88ccd192e90ce1b135d6 0.600000000000 1390419 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": 932493, "vin": [ { "gen": { "height": 932483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5a10dba1cde32a4862e73914e9cda898c86c134630f88ccd192e90ce1b135d6" } } ], "extra": [ 1, 33, 108, 36, 45, 15, 210, 101, 41, 109, 61, 162, 170, 41, 68, 255, 91, 67, 109, 148, 176, 1, 134, 49, 141, 197, 12, 74, 14, 90, 24, 16, 95, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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