Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7634641535bb2c58719e82754bc179d28197bd34ef470e5800397f4e2ff1c6d0

Tx prefix hash: 895db24aef9a7256bdbab7139d22ce34c5869cc06351310da7f5120c52331324
Tx public key: dc5aecd86020a1e3bcf209aab633f8668206c15aaade83d2740c3de6d9f6e6e8
Timestamp: 1708069215 Timestamp [UCT]: 2024-02-16 07:40:15 Age [y:d:h:m:s]: 01:047:17:52:19
Block: 958633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295160 RingCT/type: yes/0
Extra: 01dc5aecd86020a1e3bcf209aab633f8668206c15aaade83d2740c3de6d9f6e6e802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bf0dce0bd9b39ece12cc0fad40f412fe818a4e01c9f0ddd3ee618f099cad4d9 0.600000000000 1417992 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": 958643, "vin": [ { "gen": { "height": 958633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bf0dce0bd9b39ece12cc0fad40f412fe818a4e01c9f0ddd3ee618f099cad4d9" } } ], "extra": [ 1, 220, 90, 236, 216, 96, 32, 161, 227, 188, 242, 9, 170, 182, 51, 248, 102, 130, 6, 193, 90, 170, 222, 131, 210, 116, 12, 61, 230, 217, 246, 230, 232, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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