Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2faf3619f33cbc902cb9201bd83491b38292fcc4e3bbdb3c7a143a4746a9b9fc

Tx prefix hash: 65b455e471073d62851f04410ae8489346f35942316c93cd4ee691374e9bdd97
Tx public key: e37813d0d8e4eba9959bb48c73fb9d91daef50a44366856b1e99bebeec99a498
Timestamp: 1744066326 Timestamp [UCT]: 2025-04-07 22:52:06 Age [y:d:h:m:s]: 00:224:19:00:02
Block: 1256569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158405 RingCT/type: yes/0
Extra: 01e37813d0d8e4eba9959bb48c73fb9d91daef50a44366856b1e99bebeec99a49802110000000c6c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd460ae6c3acc2f1877b5cafd5f758c0f415c441e1cc051fa84d1873740b80c1 0.600000000000 1743684 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": 1256579, "vin": [ { "gen": { "height": 1256569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd460ae6c3acc2f1877b5cafd5f758c0f415c441e1cc051fa84d1873740b80c1" } } ], "extra": [ 1, 227, 120, 19, 208, 216, 228, 235, 169, 149, 155, 180, 140, 115, 251, 157, 145, 218, 239, 80, 164, 67, 102, 133, 107, 30, 153, 190, 190, 236, 153, 164, 152, 2, 17, 0, 0, 0, 12, 108, 152, 170, 61, 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