Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d63ebd53d443ff4befe6f46e1ac16c9b756faee723e1e8c40cb183db84e2e59f

Tx prefix hash: 34820861c831083f275c17fa1b9040ea0744c760052b50f48412cfd5acdcba99
Tx public key: ba71202418e085261a40d773f6c05e3dc85c15b1e488d031228830fd9b695d15
Timestamp: 1733678216 Timestamp [UCT]: 2024-12-08 17:16:56 Age [y:d:h:m:s]: 00:106:18:55:44
Block: 1170865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76099 RingCT/type: yes/0
Extra: 01ba71202418e085261a40d773f6c05e3dc85c15b1e488d031228830fd9b695d1502110000000e007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c499af6c4e3e232fdfade149757cdad164e2d6714b62baf3235a38afbf26f41 0.600000000000 1656600 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": 1170875, "vin": [ { "gen": { "height": 1170865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c499af6c4e3e232fdfade149757cdad164e2d6714b62baf3235a38afbf26f41" } } ], "extra": [ 1, 186, 113, 32, 36, 24, 224, 133, 38, 26, 64, 215, 115, 246, 192, 94, 61, 200, 92, 21, 177, 228, 136, 208, 49, 34, 136, 48, 253, 155, 105, 93, 21, 2, 17, 0, 0, 0, 14, 0, 127, 151, 138, 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