Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9f5460644542ff01004700d48bc190c62402a1495c212e32382c213caf7cea8

Tx prefix hash: e105f458e9d75119d1174ca768d86a7b405a6c741c550331db602f3af22f425c
Tx public key: a30322ae1fe995f2164ea808aaecf8402e728138bed4c611ffc49d14f4850cb3
Timestamp: 1738326126 Timestamp [UCT]: 2025-01-31 12:22:06 Age [y:d:h:m:s]: 00:293:10:07:29
Block: 1209062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207468 RingCT/type: yes/0
Extra: 01a30322ae1fe995f2164ea808aaecf8402e728138bed4c611ffc49d14f4850cb30211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6360b3ccdaf4a2e2bc333067a03ad6f691cdcec22d8c6423e50b362b8926665 0.600000000000 1695803 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": 1209072, "vin": [ { "gen": { "height": 1209062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6360b3ccdaf4a2e2bc333067a03ad6f691cdcec22d8c6423e50b362b8926665" } } ], "extra": [ 1, 163, 3, 34, 174, 31, 233, 149, 242, 22, 78, 168, 8, 170, 236, 248, 64, 46, 114, 129, 56, 190, 212, 198, 17, 255, 196, 157, 20, 244, 133, 12, 179, 2, 17, 0, 0, 0, 4, 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