Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 086c3ff7ca2844f827b8de713b7ea65b4f58328eeae7484a4cfe962fdce62faf

Tx prefix hash: dd893b1af36d59a1f02e13703a3bcd1ccaa4f32e33c1239844e6d491a0ed164c
Tx public key: dc962d539429e2cf154bfe1ba5766b6d3b4d70d0ea2d00b7f960ae3b6ed0ce9c
Timestamp: 1734545465 Timestamp [UCT]: 2024-12-18 18:11:05 Age [y:d:h:m:s]: 00:108:23:31:53
Block: 1178059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77643 RingCT/type: yes/0
Extra: 01dc962d539429e2cf154bfe1ba5766b6d3b4d70d0ea2d00b7f960ae3b6ed0ce9c0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac76d64a390198657120717e2427013352aa0612c0823752c3be3831435a09f2 0.600000000000 1664442 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": 1178069, "vin": [ { "gen": { "height": 1178059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac76d64a390198657120717e2427013352aa0612c0823752c3be3831435a09f2" } } ], "extra": [ 1, 220, 150, 45, 83, 148, 41, 226, 207, 21, 75, 254, 27, 165, 118, 107, 109, 59, 77, 112, 208, 234, 45, 0, 183, 249, 96, 174, 59, 110, 208, 206, 156, 2, 17, 0, 0, 0, 6, 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