Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff4308abdc89dfd667adcc9c6a7000ce05aa1c61afa8dc16380c3a9d58ecc05a

Tx prefix hash: 6196642fd8926a991dbf0c7ff144f9380fa30bce99d07c87577c94af9086c027
Tx public key: 50e0532c393a2721498f8b41f70bddc0b0a1d17a1be61c096f4a7d908846fb47
Timestamp: 1734336427 Timestamp [UCT]: 2024-12-16 08:07:07 Age [y:d:h:m:s]: 00:149:09:07:32
Block: 1176317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106566 RingCT/type: yes/0
Extra: 0150e0532c393a2721498f8b41f70bddc0b0a1d17a1be61c096f4a7d908846fb47021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21f6f057615c3dcca9e34bb41a6b409ff9867eb97443862468d633ef4db5217c 0.600000000000 1662648 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": 1176327, "vin": [ { "gen": { "height": 1176317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21f6f057615c3dcca9e34bb41a6b409ff9867eb97443862468d633ef4db5217c" } } ], "extra": [ 1, 80, 224, 83, 44, 57, 58, 39, 33, 73, 143, 139, 65, 247, 11, 221, 192, 176, 161, 209, 122, 27, 230, 28, 9, 111, 74, 125, 144, 136, 70, 251, 71, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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