Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e82c5b5fd8c7da7b70a6e1284ebe29b9b9bcc07cde956e76270864a894c4b0b7

Tx prefix hash: f78bb260ee9afbf59fe26eb8b8d4cda6510e0a72cf8aeb31f5f43abc7f44481b
Tx public key: 99cfbf08487870770f30a6a3823f415c4d8f47e98e66ba679f874601dc9d9cba
Timestamp: 1712567151 Timestamp [UCT]: 2024-04-08 09:05:51 Age [y:d:h:m:s]: 01:071:14:54:21
Block: 995901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312078 RingCT/type: yes/0
Extra: 0199cfbf08487870770f30a6a3823f415c4d8f47e98e66ba679f874601dc9d9cba02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 554748d68995fa75d63d24556ee64dcfd5c7888d64bd8a2cd31f988da4e28d52 0.600000000000 1456315 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": 995911, "vin": [ { "gen": { "height": 995901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "554748d68995fa75d63d24556ee64dcfd5c7888d64bd8a2cd31f988da4e28d52" } } ], "extra": [ 1, 153, 207, 191, 8, 72, 120, 112, 119, 15, 48, 166, 163, 130, 63, 65, 92, 77, 143, 71, 233, 142, 102, 186, 103, 159, 135, 70, 1, 220, 157, 156, 186, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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