Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df68646e3b515a0d16a8a857be27471722ba4e48079fb7097aeb50495e468f8b

Tx prefix hash: 56cfc0774f7a6bc4a3359853c460a6f972e7f697c6563a9f1a1512414eb70b88
Tx public key: 7974d2df0d85ab30719c4661b57734ae8bcd5072765c4b1bf8eeca57ee0c32b7
Timestamp: 1712558394 Timestamp [UCT]: 2024-04-08 06:39:54 Age [y:d:h:m:s]: 01:068:00:27:04
Block: 995838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309530 RingCT/type: yes/0
Extra: 017974d2df0d85ab30719c4661b57734ae8bcd5072765c4b1bf8eeca57ee0c32b702110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bebba2815f382dc841907d63cd403d173b06a8d6a536b4561e987d59b491e346 0.600000000000 1456252 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": 995848, "vin": [ { "gen": { "height": 995838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bebba2815f382dc841907d63cd403d173b06a8d6a536b4561e987d59b491e346" } } ], "extra": [ 1, 121, 116, 210, 223, 13, 133, 171, 48, 113, 156, 70, 97, 181, 119, 52, 174, 139, 205, 80, 114, 118, 92, 75, 27, 248, 238, 202, 87, 238, 12, 50, 183, 2, 17, 0, 0, 0, 5, 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