Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6280f06aa5a2149a3dddd0f343fbd4fb6796833a5c8049234f036f15f5b74810

Tx prefix hash: 925035afbc18dc7bcf6c71f65950ecd614dd483ab5a036b0ee0aa371bf99c31c
Tx public key: c795383a044757293e2861e71f3fc107baa84ce40c06990b3dafe4b3d79c5532
Timestamp: 1755685523 Timestamp [UCT]: 2025-08-20 10:25:23 Age [y:d:h:m:s]: 00:092:10:07:40
Block: 1350518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65953 RingCT/type: yes/0
Extra: 01c795383a044757293e2861e71f3fc107baa84ce40c06990b3dafe4b3d79c5532021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b7503fb9dc0a02d9af39f9c1acaf3f1c58b0d9a81d73175cdfd1f9bf7a583f7 0.600000000000 1838463 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": 1350528, "vin": [ { "gen": { "height": 1350518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b7503fb9dc0a02d9af39f9c1acaf3f1c58b0d9a81d73175cdfd1f9bf7a583f7" } } ], "extra": [ 1, 199, 149, 56, 58, 4, 71, 87, 41, 62, 40, 97, 231, 31, 63, 193, 7, 186, 168, 76, 228, 12, 6, 153, 11, 61, 175, 228, 179, 215, 156, 85, 50, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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