Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ea20d90b5eef50b11672e63a2099dd16a8739f693e7c1097ae7b51098770b9a

Tx prefix hash: c8a35a15364abe040021e98215f1cd03c2cef92f71efcc6059454203beaa5116
Tx public key: 5e4c528a19147300c3c06f2333ec8508d92b643e885ece6c3ea41f3e513fc233
Timestamp: 1708116264 Timestamp [UCT]: 2024-02-16 20:44:24 Age [y:d:h:m:s]: 01:038:16:57:28
Block: 959027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288689 RingCT/type: yes/0
Extra: 015e4c528a19147300c3c06f2333ec8508d92b643e885ece6c3ea41f3e513fc23302110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f3bf2b98a7eb5df4fcbf3acc8d147ac830914e7446e7ad085d1434e56b33199 0.600000000000 1418556 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": 959037, "vin": [ { "gen": { "height": 959027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f3bf2b98a7eb5df4fcbf3acc8d147ac830914e7446e7ad085d1434e56b33199" } } ], "extra": [ 1, 94, 76, 82, 138, 25, 20, 115, 0, 195, 192, 111, 35, 51, 236, 133, 8, 217, 43, 100, 62, 136, 94, 206, 108, 62, 164, 31, 62, 81, 63, 194, 51, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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