Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e25a77fe07cf05725cf29f2be9f01f5d007e90ede4516b61dc3ff970ac5a993

Tx prefix hash: f12c784a834806851e0f31cb16b6b2eefb7c27e4d687071d28a51f595b8f202f
Tx public key: f19f9f8239f47b77eec4054c9980c0d32bfd130c18903940ded00e8405c1eac4
Timestamp: 1740869137 Timestamp [UCT]: 2025-03-01 22:45:37 Age [y:d:h:m:s]: 00:312:10:08:52
Block: 1230102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221123 RingCT/type: yes/0
Extra: 01f19f9f8239f47b77eec4054c9980c0d32bfd130c18903940ded00e8405c1eac402110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f735e5fb38834d05d723b93b30a05e06c91660213a0a01d1edbae53feb4c581f 0.600000000000 1716997 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": 1230112, "vin": [ { "gen": { "height": 1230102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f735e5fb38834d05d723b93b30a05e06c91660213a0a01d1edbae53feb4c581f" } } ], "extra": [ 1, 241, 159, 159, 130, 57, 244, 123, 119, 238, 196, 5, 76, 153, 128, 192, 211, 43, 253, 19, 12, 24, 144, 57, 64, 222, 208, 14, 132, 5, 193, 234, 196, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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