Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9415f8807890144958e31175ae798073a17c248d47f82b7b923f9c7116e0386d

Tx prefix hash: ed154daea2f7a92308f494d25d6dc62b8aa116f5e99e7532ceb343e909b88378
Tx public key: 115a5125956add4f3a55162eead4740dff6f7069147f34ac16523eff8e7e34d3
Timestamp: 1727443765 Timestamp [UCT]: 2024-09-27 13:29:25 Age [y:d:h:m:s]: 00:184:10:20:42
Block: 1119264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131617 RingCT/type: yes/0
Extra: 01115a5125956add4f3a55162eead4740dff6f7069147f34ac16523eff8e7e34d3021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f0ae02c83223d3aece252dbcf84b68dc1f9ebe4290b670d0be0f399ea3250b6 0.600000000000 1600761 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": 1119274, "vin": [ { "gen": { "height": 1119264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f0ae02c83223d3aece252dbcf84b68dc1f9ebe4290b670d0be0f399ea3250b6" } } ], "extra": [ 1, 17, 90, 81, 37, 149, 106, 221, 79, 58, 85, 22, 46, 234, 212, 116, 13, 255, 111, 112, 105, 20, 127, 52, 172, 22, 82, 62, 255, 142, 126, 52, 211, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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