Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 494f32c13b3cdd0c3a90a6481a52df440f402a96ab2241d81291535e540c7e41

Tx prefix hash: 8a40457714fa97c40a286e8073916e06cd66436cd23acef3b152599a07e9c090
Tx public key: 5d5089b3188ac98eb5a29e2aad3a34dea5a57120cae74c6e0ed30bebc9de6fd5
Timestamp: 1713969056 Timestamp [UCT]: 2024-04-24 14:30:56 Age [y:d:h:m:s]: 00:308:18:35:07
Block: 1007553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220713 RingCT/type: yes/0
Extra: 015d5089b3188ac98eb5a29e2aad3a34dea5a57120cae74c6e0ed30bebc9de6fd50211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c2a8a1296a1f873f8187ca7cafbb3c0878d47763ee455300fa766ebbcc657e7 0.600000000000 1468937 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": 1007563, "vin": [ { "gen": { "height": 1007553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c2a8a1296a1f873f8187ca7cafbb3c0878d47763ee455300fa766ebbcc657e7" } } ], "extra": [ 1, 93, 80, 137, 179, 24, 138, 201, 142, 181, 162, 158, 42, 173, 58, 52, 222, 165, 165, 113, 32, 202, 231, 76, 110, 14, 211, 11, 235, 201, 222, 111, 213, 2, 17, 0, 0, 0, 6, 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