Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3d1e3cdd8d49b6e791a6b8fb5e436fabb71d1efc556e213a0d7e01be8b21d46

Tx prefix hash: 638e054e04f5900d92f79d1408d7064708272a9c0b049672c458a8cc47bf7bf7
Tx public key: b967e74596dc193315783c5cf3f2b1f498097a08b8ed6219b85454de29fed302
Timestamp: 1711153890 Timestamp [UCT]: 2024-03-23 00:31:30 Age [y:d:h:m:s]: 00:361:10:33:12
Block: 984243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258419 RingCT/type: yes/0
Extra: 01b967e74596dc193315783c5cf3f2b1f498097a08b8ed6219b85454de29fed3020211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd7bbffbce460c79fcbc22a45d98224560190ec5e48ff286e37c6a866fb8a4a2 0.600000000000 1444410 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": 984253, "vin": [ { "gen": { "height": 984243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd7bbffbce460c79fcbc22a45d98224560190ec5e48ff286e37c6a866fb8a4a2" } } ], "extra": [ 1, 185, 103, 231, 69, 150, 220, 25, 51, 21, 120, 60, 92, 243, 242, 177, 244, 152, 9, 122, 8, 184, 237, 98, 25, 184, 84, 84, 222, 41, 254, 211, 2, 2, 17, 0, 0, 0, 5, 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