Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 751fd806c02664fb2de663f01f9bfd3cb101b47cf2a7a36bebadcbe18c8196a6

Tx prefix hash: 3b99d6049287609987b810aca49b1ec5dddc2c76122f641c221bb895b8f13051
Tx public key: 5763c24aede6a04c4ee4e5d0839a31f26e344b5231075aad198e65b974c6f1f2
Timestamp: 1747037382 Timestamp [UCT]: 2025-05-12 08:09:42 Age [y:d:h:m:s]: 00:182:13:29:01
Block: 1281172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128179 RingCT/type: yes/0
Extra: 015763c24aede6a04c4ee4e5d0839a31f26e344b5231075aad198e65b974c6f1f20211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db457fddcc0f5c189dc23a3e2cedcb380bb6749982b85caf9b547e2e28c9ac66 0.600000000000 1768571 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": 1281182, "vin": [ { "gen": { "height": 1281172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db457fddcc0f5c189dc23a3e2cedcb380bb6749982b85caf9b547e2e28c9ac66" } } ], "extra": [ 1, 87, 99, 194, 74, 237, 230, 160, 76, 78, 228, 229, 208, 131, 154, 49, 242, 110, 52, 75, 82, 49, 7, 90, 173, 25, 142, 101, 185, 116, 198, 241, 242, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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