Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72e33c742ad25e0267ed53f9b40fc6996e912b9a84f0d3e64aa96fe7a079e50a

Tx prefix hash: de8ffc58bc0b55e3a803a02a4a6e06f678b53aa46c0be821b73bb6004e29b1ce
Tx public key: 6c8edb69574f093f99958b4f25f2b1c68982dfe506bdf79bb182a96f198dc74c
Timestamp: 1704226693 Timestamp [UCT]: 2024-01-02 20:18:13 Age [y:d:h:m:s]: 01:308:05:32:40
Block: 926784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479097 RingCT/type: yes/0
Extra: 016c8edb69574f093f99958b4f25f2b1c68982dfe506bdf79bb182a96f198dc74c02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb3f084ce62db429b68457a24d50fd57974b07237430c43d88b6813a0b05a304 0.600000000000 1384582 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": 926794, "vin": [ { "gen": { "height": 926784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb3f084ce62db429b68457a24d50fd57974b07237430c43d88b6813a0b05a304" } } ], "extra": [ 1, 108, 142, 219, 105, 87, 79, 9, 63, 153, 149, 139, 79, 37, 242, 177, 198, 137, 130, 223, 229, 6, 189, 247, 155, 177, 130, 169, 111, 25, 141, 199, 76, 2, 17, 0, 0, 0, 2, 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