Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 460a584cf7d72bd3bd1fd3df7d077cbeae1f6a0b37b167499e7d101d1ceb020a

Tx prefix hash: f3ff8acdb99e804e4900568112ef29786e401b557e929842f346d19e4169e89b
Tx public key: e741e6a8f3d9255de298ccfa10258e21850ffe31d8b8394ecbcc221210a53579
Timestamp: 1705389903 Timestamp [UCT]: 2024-01-16 07:25:03 Age [y:d:h:m:s]: 00:360:13:46:09
Block: 936404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258169 RingCT/type: yes/0
Extra: 01e741e6a8f3d9255de298ccfa10258e21850ffe31d8b8394ecbcc221210a535790211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9161b7f287c17df8f9d2b608ea4b69b6d22eabff471001f8487c042813f1c5f6 0.600000000000 1394430 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": 936414, "vin": [ { "gen": { "height": 936404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9161b7f287c17df8f9d2b608ea4b69b6d22eabff471001f8487c042813f1c5f6" } } ], "extra": [ 1, 231, 65, 230, 168, 243, 217, 37, 93, 226, 152, 204, 250, 16, 37, 142, 33, 133, 15, 254, 49, 216, 184, 57, 78, 203, 204, 34, 18, 16, 165, 53, 121, 2, 17, 0, 0, 0, 7, 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