Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e9aedeb8a70a85348c1c06339244b53e2e9eb668f387ffea71781e19fa6fef6

Tx prefix hash: a599d887c4143366e454d66e49c3118af872b57538abaaba89438d4ccb4ee0b1
Tx public key: b253ae9ebf3de1d1b0ee8edead8396c94c9cdf8069369a710fe56ab0a2a0bf9c
Timestamp: 1713945021 Timestamp [UCT]: 2024-04-24 07:50:21 Age [y:d:h:m:s]: 00:190:17:03:08
Block: 1007359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136527 RingCT/type: yes/0
Extra: 01b253ae9ebf3de1d1b0ee8edead8396c94c9cdf8069369a710fe56ab0a2a0bf9c0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 754f14727b9cd020a73f6fcbed80641fc724367110315c579db78f19653b7d9b 0.600000000000 1468673 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": 1007369, "vin": [ { "gen": { "height": 1007359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "754f14727b9cd020a73f6fcbed80641fc724367110315c579db78f19653b7d9b" } } ], "extra": [ 1, 178, 83, 174, 158, 191, 61, 225, 209, 176, 238, 142, 222, 173, 131, 150, 201, 76, 156, 223, 128, 105, 54, 154, 113, 15, 229, 106, 176, 162, 160, 191, 156, 2, 17, 0, 0, 0, 2, 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