Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a53ac63fd9cdc1c5f5b3a9b0ca92735bdac248723288f2373cb938216dd7b4e

Tx prefix hash: e1c8e47bef6541e9314cb345f9a69dd7e6b683167f839fae8b7529e5fcbbf7d9
Tx public key: 94e92b578ed3841de80827b2f4ac6339642987327c2d7397d9b85adc774d4021
Timestamp: 1751628910 Timestamp [UCT]: 2025-07-04 11:35:10 Age [y:d:h:m:s]: 00:128:19:56:47
Block: 1318565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90371 RingCT/type: yes/0
Extra: 0194e92b578ed3841de80827b2f4ac6339642987327c2d7397d9b85adc774d4021021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 465ebccc5885cf5c364c8021afc00b72ba66dc72e7e5e99e93b4aec8a81d5f8c 0.600000000000 1806250 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": 1318575, "vin": [ { "gen": { "height": 1318565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "465ebccc5885cf5c364c8021afc00b72ba66dc72e7e5e99e93b4aec8a81d5f8c" } } ], "extra": [ 1, 148, 233, 43, 87, 142, 211, 132, 29, 232, 8, 39, 178, 244, 172, 99, 57, 100, 41, 135, 50, 124, 45, 115, 151, 217, 184, 90, 220, 119, 77, 64, 33, 2, 17, 0, 0, 0, 1, 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