Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f72805f695d4a6889ba7c3f1d67a70722e8b69369dc641be2d233193b2443ec

Tx prefix hash: c4ee87029eb9cbebb131c272b40a6aca4c0e890e18d8137f044eed61dfce1279
Tx public key: 22a9fd1df23b9c8861ece5f937da77d6722d6ce137280982f69f97eae603b11a
Timestamp: 1706104123 Timestamp [UCT]: 2024-01-24 13:48:43 Age [y:d:h:m:s]: 01:151:14:30:06
Block: 942326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369252 RingCT/type: yes/0
Extra: 0122a9fd1df23b9c8861ece5f937da77d6722d6ce137280982f69f97eae603b11a0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e270ef7d121758b4ae07ce249b406623522591944aab9e538af8910f601d09c3 0.600000000000 1400496 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": 942336, "vin": [ { "gen": { "height": 942326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e270ef7d121758b4ae07ce249b406623522591944aab9e538af8910f601d09c3" } } ], "extra": [ 1, 34, 169, 253, 29, 242, 59, 156, 136, 97, 236, 229, 249, 55, 218, 119, 214, 114, 45, 108, 225, 55, 40, 9, 130, 246, 159, 151, 234, 230, 3, 177, 26, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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