Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef25e882158d160422484fa8f688311c173a215d8b1d645e4c6b656b83f84033

Tx prefix hash: e86b7456a06f1cd7046ee2e08457c67ec5a4a66f8c4c8c3b32f2cd6d153790dc
Tx public key: bee6a77978dff04152de5fb06724f42e7c7c898235ff54a175643dd7a7401e6f
Timestamp: 1736497724 Timestamp [UCT]: 2025-01-10 08:28:44 Age [y:d:h:m:s]: 00:098:06:11:30
Block: 1194186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70022 RingCT/type: yes/0
Extra: 01bee6a77978dff04152de5fb06724f42e7c7c898235ff54a175643dd7a7401e6f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc3336b181b79addbe899eb91338a879f38e7b7d072512b9ba9edef1bca8b555 0.600000000000 1680753 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": 1194196, "vin": [ { "gen": { "height": 1194186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc3336b181b79addbe899eb91338a879f38e7b7d072512b9ba9edef1bca8b555" } } ], "extra": [ 1, 190, 230, 167, 121, 120, 223, 240, 65, 82, 222, 95, 176, 103, 36, 244, 46, 124, 124, 137, 130, 53, 255, 84, 161, 117, 100, 61, 215, 167, 64, 30, 111, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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