Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d635e52ad18b5cbc32a1c82a200e93e8ce701af370cc02721b825812a0beb84

Tx prefix hash: 90da2d7e178974db72011122357353737c4c57fc897fb8f5d414b50d300ce945
Tx public key: 02e41b82bfc1045cb239e7e1af34cbbb1ccea18d9b4ce03448aa4bf6f4e85357
Timestamp: 1708503173 Timestamp [UCT]: 2024-02-21 08:12:53 Age [y:d:h:m:s]: 01:115:14:37:59
Block: 962241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343594 RingCT/type: yes/0
Extra: 0102e41b82bfc1045cb239e7e1af34cbbb1ccea18d9b4ce03448aa4bf6f4e853570211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d5e97312aae502cff349dd64e3b51afa3e2e8203a62b2f4aac14703b28a1d31 0.600000000000 1421868 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": 962251, "vin": [ { "gen": { "height": 962241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d5e97312aae502cff349dd64e3b51afa3e2e8203a62b2f4aac14703b28a1d31" } } ], "extra": [ 1, 2, 228, 27, 130, 191, 193, 4, 92, 178, 57, 231, 225, 175, 52, 203, 187, 28, 206, 161, 141, 155, 76, 224, 52, 72, 170, 75, 246, 244, 232, 83, 87, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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