Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dde82f08743e23651b4284c1e36bb9cd8c1c099481d3e093cb9f685f59d389de

Tx prefix hash: 58d8b6440c8a7fd28baacd3b1757d1acaa8e820e1cd634fe8611247a4e6e4533
Tx public key: aec12ede8fa6a73cf5ac8c4189d163c8ce339ac84be5f6df1d8282512b62a2c5
Timestamp: 1739019979 Timestamp [UCT]: 2025-02-08 13:06:19 Age [y:d:h:m:s]: 00:284:02:30:24
Block: 1214809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200801 RingCT/type: yes/0
Extra: 01aec12ede8fa6a73cf5ac8c4189d163c8ce339ac84be5f6df1d8282512b62a2c5021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e08ec06c45c8f23a8e471c20b9db62dedeeea474339666fdaa0f641cfe9f5542 0.600000000000 1701604 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": 1214819, "vin": [ { "gen": { "height": 1214809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e08ec06c45c8f23a8e471c20b9db62dedeeea474339666fdaa0f641cfe9f5542" } } ], "extra": [ 1, 174, 193, 46, 222, 143, 166, 167, 60, 245, 172, 140, 65, 137, 209, 99, 200, 206, 51, 154, 200, 75, 229, 246, 223, 29, 130, 130, 81, 43, 98, 162, 197, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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