Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a31a5de4ad4db3487c60e8514d0819972710ae63a03aa6825585c1ca232906b

Tx prefix hash: 655bf621bdf1b9b991be3aabf61f3aeddbba997fa42df336ff943d9f39d4f3c9
Tx public key: f6446ecce934d62d0dd6fbcc6fa3b2a5d15b547f97c562d0769e14cafc0eab9d
Timestamp: 1749860926 Timestamp [UCT]: 2025-06-14 00:28:46 Age [y:d:h:m:s]: 00:158:15:25:29
Block: 1304475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111148 RingCT/type: yes/0
Extra: 01f6446ecce934d62d0dd6fbcc6fa3b2a5d15b547f97c562d0769e14cafc0eab9d0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ef99e6b12bbdb1cd2c4815a8b693993253d42dfdf4417463e083968d30678fe 0.600000000000 1792064 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": 1304485, "vin": [ { "gen": { "height": 1304475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ef99e6b12bbdb1cd2c4815a8b693993253d42dfdf4417463e083968d30678fe" } } ], "extra": [ 1, 246, 68, 110, 204, 233, 52, 214, 45, 13, 214, 251, 204, 111, 163, 178, 165, 209, 91, 84, 127, 151, 197, 98, 208, 118, 158, 20, 202, 252, 14, 171, 157, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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