Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08d339a78b32e1a5bcd1c56ade47140bc2e3cd56be28e0563704c0992256f241

Tx prefix hash: d8abd331fd57a3811d6b35d125432b199a5d9aa0eb066fcd3437326d1b0fa5d2
Tx public key: 36a62668f10527ccbcf12ee844f90e8cacc7b1d3e85fda62c2de1bd42bbe6cb3
Timestamp: 1755929007 Timestamp [UCT]: 2025-08-23 06:03:27 Age [y:d:h:m:s]: 00:089:01:58:02
Block: 1352500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63605 RingCT/type: yes/0
Extra: 0136a62668f10527ccbcf12ee844f90e8cacc7b1d3e85fda62c2de1bd42bbe6cb30211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ebcb0cd539f05f318ce549d591277a5897f91c5c22e4d6cd982f2ae9999e6c0 0.600000000000 1840465 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": 1352510, "vin": [ { "gen": { "height": 1352500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ebcb0cd539f05f318ce549d591277a5897f91c5c22e4d6cd982f2ae9999e6c0" } } ], "extra": [ 1, 54, 166, 38, 104, 241, 5, 39, 204, 188, 241, 46, 232, 68, 249, 14, 140, 172, 199, 177, 211, 232, 95, 218, 98, 194, 222, 27, 212, 43, 190, 108, 179, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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