Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9acef1075a6bd3462bfb9835565d1448dab97d3427c3c9c0d5ed6936bcdec77

Tx prefix hash: 018a312d3f679d67e4394635f6a9385a997ab6bad89eb9c34a477b5e7a502d55
Tx public key: efd30a80cb5dfdd55e36c279cb0d205fa396f63fd2efac5779e4a3a3af832696
Timestamp: 1729224103 Timestamp [UCT]: 2024-10-18 04:01:43 Age [y:d:h:m:s]: 00:000:10:35:33
Block: 1134028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320 RingCT/type: yes/0
Extra: 01efd30a80cb5dfdd55e36c279cb0d205fa396f63fd2efac5779e4a3a3af8326960211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37cff13683bd91653d497f0a7a94cc42f42f8f505ae2f11426ceb70aa6e51bf9 0.600000000000 1617265 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": 1134038, "vin": [ { "gen": { "height": 1134028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37cff13683bd91653d497f0a7a94cc42f42f8f505ae2f11426ceb70aa6e51bf9" } } ], "extra": [ 1, 239, 211, 10, 128, 203, 93, 253, 213, 94, 54, 194, 121, 203, 13, 32, 95, 163, 150, 246, 63, 210, 239, 172, 87, 121, 228, 163, 163, 175, 131, 38, 150, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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