Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5597af27781a9f4c9b5b7bee88817757c78058d7311fda7b661ff8ea8f1252f

Tx prefix hash: 179cbd4b5ca0414a4755bd13d0f4d7fe2a5a9883cbd1726c908df2cfc5fec502
Tx public key: 09a3a12e736aa2f3e26fa6b2917be0fcdfc343bf4587924aaf80c106cb1fbc22
Timestamp: 1698315980 Timestamp [UCT]: 2023-10-26 10:26:20 Age [y:d:h:m:s]: 01:124:10:24:43
Block: 878002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349896 RingCT/type: yes/0
Extra: 0109a3a12e736aa2f3e26fa6b2917be0fcdfc343bf4587924aaf80c106cb1fbc220211000000024b8f5122000000000000000000

1 output(s) for total of 0.756510419000 dcy

stealth address amount amount idx
00: a15f8935f65dc8e386a5c7aaf81e2dfb5d638158ee5d8c4d06f1aef29269ab31 0.756510419000 1333406 of 0

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": 878012, "vin": [ { "gen": { "height": 878002 } } ], "vout": [ { "amount": 756510419, "target": { "key": "a15f8935f65dc8e386a5c7aaf81e2dfb5d638158ee5d8c4d06f1aef29269ab31" } } ], "extra": [ 1, 9, 163, 161, 46, 115, 106, 162, 243, 226, 111, 166, 178, 145, 123, 224, 252, 223, 195, 67, 191, 69, 135, 146, 74, 175, 128, 193, 6, 203, 31, 188, 34, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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