Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a8065647fb270e335e9c5a327de6a6334214fe2748bd32e658c7a9ad3f356c6

Tx prefix hash: 786f42a2249f1abfcec377693befc14a9eb7b86a4ca3242838481a3dfaed0caf
Tx public key: 383746c4464513bbccf1e8ffb9d36d3fdb7a8ff0c66ba4f24295fe606886ee82
Timestamp: 1726607440 Timestamp [UCT]: 2024-09-17 21:10:40 Age [y:d:h:m:s]: 00:201:07:30:52
Block: 1112330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143694 RingCT/type: yes/0
Extra: 01383746c4464513bbccf1e8ffb9d36d3fdb7a8ff0c66ba4f24295fe606886ee82021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c2e4766792e78d015d8f7ae143937730aee239ca49c3fefcc3ac89ef5e2af6f 0.600000000000 1591613 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": 1112340, "vin": [ { "gen": { "height": 1112330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c2e4766792e78d015d8f7ae143937730aee239ca49c3fefcc3ac89ef5e2af6f" } } ], "extra": [ 1, 56, 55, 70, 196, 70, 69, 19, 187, 204, 241, 232, 255, 185, 211, 109, 63, 219, 122, 143, 240, 198, 107, 164, 242, 66, 149, 254, 96, 104, 134, 238, 130, 2, 17, 0, 0, 0, 3, 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