Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e65a9fcd1c6b589590fdc03137627ec9400a4165afcfd3171b9a56beb3b7f0aa

Tx prefix hash: ab9fbc0d248dfe8034f00da6fe9fc65f3d4b031a8e9a70ae7e96be8027803f39
Tx public key: e83aa605c9b1d719264833d8e68fc51ea915f463fa0d285ce03ced4048458d33
Timestamp: 1717643720 Timestamp [UCT]: 2024-06-06 03:15:20 Age [y:d:h:m:s]: 00:147:02:11:08
Block: 1038017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105283 RingCT/type: yes/0
Extra: 01e83aa605c9b1d719264833d8e68fc51ea915f463fa0d285ce03ced4048458d330211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44885fc7091f0dd56fd7d50e90ff1cc0cf7d9f9aa343811362413cc672e2434f 0.600000000000 1506576 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": 1038027, "vin": [ { "gen": { "height": 1038017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44885fc7091f0dd56fd7d50e90ff1cc0cf7d9f9aa343811362413cc672e2434f" } } ], "extra": [ 1, 232, 58, 166, 5, 201, 177, 215, 25, 38, 72, 51, 216, 230, 143, 197, 30, 169, 21, 244, 99, 250, 13, 40, 92, 224, 60, 237, 64, 72, 69, 141, 51, 2, 17, 0, 0, 0, 4, 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