Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29f9c5453c067380c04f38f1dd962cf91ae2c94f16b909c4cc21ffc33b852d87

Tx prefix hash: f6a332111b263508b86338d5d09adf5c8792e7f4ff9211b429e8246f150d38ed
Tx public key: 0e3f1bf772af56b5f0d38e7ab17c28ac628d69db10f81c026a764f85d9f34bba
Timestamp: 1737895414 Timestamp [UCT]: 2025-01-26 12:43:34 Age [y:d:h:m:s]: 00:047:03:18:40
Block: 1205722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33510 RingCT/type: yes/0
Extra: 010e3f1bf772af56b5f0d38e7ab17c28ac628d69db10f81c026a764f85d9f34bba02110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8089ed8394f076904e8c043d816ef35dc5e233ca8328f314fe7112b5642be436 0.600000000000 1692421 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": 1205732, "vin": [ { "gen": { "height": 1205722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8089ed8394f076904e8c043d816ef35dc5e233ca8328f314fe7112b5642be436" } } ], "extra": [ 1, 14, 63, 27, 247, 114, 175, 86, 181, 240, 211, 142, 122, 177, 124, 40, 172, 98, 141, 105, 219, 16, 248, 28, 2, 106, 118, 79, 133, 217, 243, 75, 186, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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