Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea1cf3ccab513d712666dc1c14cbe3375e7a89388cae4223998da4c061a50a97

Tx prefix hash: dd05fc5601229a16ce28f3a56adfb97c0bac56bead3977f2ffe7f066138c8655
Tx public key: 564ba4f86c74c17f77ff87078817e7ff24db4c9cf6908e80d226d309fb2364ad
Timestamp: 1751794025 Timestamp [UCT]: 2025-07-06 09:27:05 Age [y:d:h:m:s]: 00:130:23:23:25
Block: 1319842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91998 RingCT/type: yes/0
Extra: 01564ba4f86c74c17f77ff87078817e7ff24db4c9cf6908e80d226d309fb2364ad021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5d401644b7d87b691a1de8c72a827c4a7b29c3c0311865dc6e81ae60d015822 0.600000000000 1807535 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": 1319852, "vin": [ { "gen": { "height": 1319842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5d401644b7d87b691a1de8c72a827c4a7b29c3c0311865dc6e81ae60d015822" } } ], "extra": [ 1, 86, 75, 164, 248, 108, 116, 193, 127, 119, 255, 135, 7, 136, 23, 231, 255, 36, 219, 76, 156, 246, 144, 142, 128, 210, 38, 211, 9, 251, 35, 100, 173, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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