Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a0cdcddd689901e996d26f9e392e1219b8d392e45003905c9342f3f7a0f11c5

Tx prefix hash: 7f218513419a96dc5148d8853993b7f9285a2a3d5030da36bb95cfd7efaa9c7e
Tx public key: aa8c453ee4e79bf2dadccfc36a933169c2492a08b938882bc4e59df065d0bbb3
Timestamp: 1704638010 Timestamp [UCT]: 2024-01-07 14:33:30 Age [y:d:h:m:s]: 01:119:12:12:36
Block: 930176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346541 RingCT/type: yes/0
Extra: 01aa8c453ee4e79bf2dadccfc36a933169c2492a08b938882bc4e59df065d0bbb30211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 335ffaf1899256fdfe8613d48db6f2be0409510e3b17055d50f659242ec9e281 0.600000000000 1388058 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": 930186, "vin": [ { "gen": { "height": 930176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "335ffaf1899256fdfe8613d48db6f2be0409510e3b17055d50f659242ec9e281" } } ], "extra": [ 1, 170, 140, 69, 62, 228, 231, 155, 242, 218, 220, 207, 195, 106, 147, 49, 105, 194, 73, 42, 8, 185, 56, 136, 43, 196, 229, 157, 240, 101, 208, 187, 179, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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