Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 940c319fb4571dd831a29b5b65ca68bf033a5f8fa76fe1a26707b0100e6f434a

Tx prefix hash: e8fdc14ac712e78170549c481565ab72020c0a400b4f4b3d9ab801fad2d4e7c5
Tx public key: b662e24a70bceadffb60e4e16ee043875b5ac165556d4eac6a29aba1e66046a3
Timestamp: 1755952316 Timestamp [UCT]: 2025-08-23 12:31:56 Age [y:d:h:m:s]: 00:082:16:45:26
Block: 1352696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59037 RingCT/type: yes/0
Extra: 01b662e24a70bceadffb60e4e16ee043875b5ac165556d4eac6a29aba1e66046a30211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38cd070a5e84cdd425bad16e71304d6df0076aeb5df4ba0c62f1d48356789ce3 0.600000000000 1840663 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": 1352706, "vin": [ { "gen": { "height": 1352696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38cd070a5e84cdd425bad16e71304d6df0076aeb5df4ba0c62f1d48356789ce3" } } ], "extra": [ 1, 182, 98, 226, 74, 112, 188, 234, 223, 251, 96, 228, 225, 110, 224, 67, 135, 91, 90, 193, 101, 85, 109, 78, 172, 106, 41, 171, 161, 230, 96, 70, 163, 2, 17, 0, 0, 0, 2, 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