Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a5f99d6778a92ad642002f833c36a9efae928ec0d852f3f0a4418db935adfda

Tx prefix hash: c1c3c80012527650f6fc4375e70ea762c5a149e56b625f83bd2b806f8d266beb
Tx public key: c15660cf606692ed4239a4559e1211895f213b81eaaf521fe20b117c665c77c1
Timestamp: 1705713918 Timestamp [UCT]: 2024-01-20 01:25:18 Age [y:d:h:m:s]: 01:290:23:14:17
Block: 939079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466771 RingCT/type: yes/0
Extra: 01c15660cf606692ed4239a4559e1211895f213b81eaaf521fe20b117c665c77c10211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f56e898c745bb8f429d894a4535d4bd37fe44d3e0a09dc2b11c78e8e7a6fc9c9 0.600000000000 1397163 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": 939089, "vin": [ { "gen": { "height": 939079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f56e898c745bb8f429d894a4535d4bd37fe44d3e0a09dc2b11c78e8e7a6fc9c9" } } ], "extra": [ 1, 193, 86, 96, 207, 96, 102, 146, 237, 66, 57, 164, 85, 158, 18, 17, 137, 95, 33, 59, 129, 234, 175, 82, 31, 226, 11, 17, 124, 102, 92, 119, 193, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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