Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfdfefc24c243bd865c3ab496ec08db4f342d951f287d05cec7f26629fe5611a

Tx prefix hash: 5b08a1f8e1034a4a52e9ffafd51c5d3b7e06de1d12d2d853e837932bc2a5252c
Tx public key: 1609c097e1d6fae5dc2160240fa50791118996436f713571e8f649009307ad59
Timestamp: 1696936738 Timestamp [UCT]: 2023-10-10 11:18:58 Age [y:d:h:m:s]: 01:139:13:20:23
Block: 866560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360733 RingCT/type: yes/0
Extra: 011609c097e1d6fae5dc2160240fa50791118996436f713571e8f649009307ad590211000000024b8f5122000000000000000000

1 output(s) for total of 0.825518910000 dcy

stealth address amount amount idx
00: 6925f909f8e378d53bbdfb56f9688d0d58397fd71a8dadf9ae1278c486f16ae8 0.825518910000 1321166 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": 866570, "vin": [ { "gen": { "height": 866560 } } ], "vout": [ { "amount": 825518910, "target": { "key": "6925f909f8e378d53bbdfb56f9688d0d58397fd71a8dadf9ae1278c486f16ae8" } } ], "extra": [ 1, 22, 9, 192, 151, 225, 214, 250, 229, 220, 33, 96, 36, 15, 165, 7, 145, 17, 137, 150, 67, 111, 113, 53, 113, 232, 246, 73, 0, 147, 7, 173, 89, 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