Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8776e3ccd4003e0670d8575035007afeed13065677b299f98cf42a9bb4ecf5c7

Tx prefix hash: 1fabe27f0d3f0ae6d5b0f052c91e3f09c13171fb398b37d67fed98e0b6d66e59
Tx public key: b6ef51303f1a50bbfb3ce9d67a36217bfcf3e1b27a11c2284ae5cccd91fb082d
Timestamp: 1725572483 Timestamp [UCT]: 2024-09-05 21:41:23 Age [y:d:h:m:s]: 00:234:06:05:01
Block: 1103757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167281 RingCT/type: yes/0
Extra: 01b6ef51303f1a50bbfb3ce9d67a36217bfcf3e1b27a11c2284ae5cccd91fb082d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 065446de788b59c13334070b3fd0972e07c2e5ce1b6e1b6d69480e3ba5cad2d1 0.600000000000 1580710 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": 1103767, "vin": [ { "gen": { "height": 1103757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "065446de788b59c13334070b3fd0972e07c2e5ce1b6e1b6d69480e3ba5cad2d1" } } ], "extra": [ 1, 182, 239, 81, 48, 63, 26, 80, 187, 251, 60, 233, 214, 122, 54, 33, 123, 252, 243, 225, 178, 122, 17, 194, 40, 74, 229, 204, 205, 145, 251, 8, 45, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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