Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac816aef104289a728073697ac59b6e71c38f769a61b70985079cebb61146453

Tx prefix hash: 57902fd7b961f6d6097c52a6f4bb20776e502faa7eb348a6c44a593fc4c7fa82
Tx public key: e06bd8732f909b733dba498a975e724d5c136cff70bbd6687b6898ba2db6f818
Timestamp: 1750285137 Timestamp [UCT]: 2025-06-18 22:18:57 Age [y:d:h:m:s]: 00:154:21:03:33
Block: 1307930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108511 RingCT/type: yes/0
Extra: 01e06bd8732f909b733dba498a975e724d5c136cff70bbd6687b6898ba2db6f81802110000000ebf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a07f7e55c3ec1e7b59d9db893d26846f3dc0d07459591ec5d03d729369e83ae 0.600000000000 1795541 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": 1307940, "vin": [ { "gen": { "height": 1307930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a07f7e55c3ec1e7b59d9db893d26846f3dc0d07459591ec5d03d729369e83ae" } } ], "extra": [ 1, 224, 107, 216, 115, 47, 144, 155, 115, 61, 186, 73, 138, 151, 94, 114, 77, 92, 19, 108, 255, 112, 187, 214, 104, 123, 104, 152, 186, 45, 182, 248, 24, 2, 17, 0, 0, 0, 14, 191, 81, 178, 162, 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