Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a77ee9b4c70d443220b7a11dcc4e9fc8e86d19cce669fd88f8ba51b0d1ac2fdf

Tx prefix hash: 8daf2698adf56c3910b72fcf6943a6642da8350c323d301ba75592917259e5f9
Tx public key: 1eb267426ea0d9422e0eddf64ae0de21933ecc4fd90062276e7f45a2f0a8b067
Timestamp: 1719670315 Timestamp [UCT]: 2024-06-29 14:11:55 Age [y:d:h:m:s]: 01:184:18:13:14
Block: 1054823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390649 RingCT/type: yes/0
Extra: 011eb267426ea0d9422e0eddf64ae0de21933ecc4fd90062276e7f45a2f0a8b06702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8136218a4ca44a017b326777b797c07255b935359a3d6853939bc5bbbc1ee03 0.600000000000 1525214 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": 1054833, "vin": [ { "gen": { "height": 1054823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8136218a4ca44a017b326777b797c07255b935359a3d6853939bc5bbbc1ee03" } } ], "extra": [ 1, 30, 178, 103, 66, 110, 160, 217, 66, 46, 14, 221, 246, 74, 224, 222, 33, 147, 62, 204, 79, 217, 0, 98, 39, 110, 127, 69, 162, 240, 168, 176, 103, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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