Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96a9e2b3065ff98f757c9f176d8daaf68ac55c5946ef390bed0c9877c946a4ae

Tx prefix hash: c8991399ddbdbf94495ff6c4c3a02e9588005388d6256b6262f47a037cfb262a
Tx public key: 764bc159e233cb2181911a2d433e198c6914248f8a8f7d36eb9c6f516c35b0af
Timestamp: 1703992790 Timestamp [UCT]: 2023-12-31 03:19:50 Age [y:d:h:m:s]: 01:094:19:59:17
Block: 924834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328894 RingCT/type: yes/0
Extra: 01764bc159e233cb2181911a2d433e198c6914248f8a8f7d36eb9c6f516c35b0af0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ac882d60acdeccf20905305b4a9bc5a2bd05e35a244897d3d6ee9944cfbbab3 0.600000000000 1382594 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": 924844, "vin": [ { "gen": { "height": 924834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ac882d60acdeccf20905305b4a9bc5a2bd05e35a244897d3d6ee9944cfbbab3" } } ], "extra": [ 1, 118, 75, 193, 89, 226, 51, 203, 33, 129, 145, 26, 45, 67, 62, 25, 140, 105, 20, 36, 143, 138, 143, 125, 54, 235, 156, 111, 81, 108, 53, 176, 175, 2, 17, 0, 0, 0, 6, 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