Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66a57178c33ab9f6bba9a0b142eb7ed211b125b6bd6fb93c26ce25e48146c14d

Tx prefix hash: 0ee609a243e5e285b2c0a8cf7f0c276c0f359cc4697da3e0e023c1d1fb467a31
Tx public key: ac242deedfc2ac592292a228e906301111fd213f724f3c21c919fb8aed7bb014
Timestamp: 1747673076 Timestamp [UCT]: 2025-05-19 16:44:36 Age [y:d:h:m:s]: 00:141:10:02:31
Block: 1286443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98707 RingCT/type: yes/0
Extra: 01ac242deedfc2ac592292a228e906301111fd213f724f3c21c919fb8aed7bb0140211000000081f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b62fedeb31681883fc364b2e3dbdbfccc2736eddcf619cb45a38c042e4fe969 0.600000000000 1773908 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": 1286453, "vin": [ { "gen": { "height": 1286443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b62fedeb31681883fc364b2e3dbdbfccc2736eddcf619cb45a38c042e4fe969" } } ], "extra": [ 1, 172, 36, 45, 238, 223, 194, 172, 89, 34, 146, 162, 40, 233, 6, 48, 17, 17, 253, 33, 63, 114, 79, 60, 33, 201, 25, 251, 138, 237, 123, 176, 20, 2, 17, 0, 0, 0, 8, 31, 144, 81, 122, 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