Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4609f9f2d7fe732b8ee5102c701cbc21acd811be9c6c43ea4886b6af871176e5

Tx prefix hash: 43046d2e566beaee9b7dbbf86ce298c429c9a98ad85f75059712d680cf33cede
Tx public key: b8ae6d74f03a6f2f1ed57d9744283438de9ba6ec1ae045de4377bab468928bbc
Timestamp: 1719772596 Timestamp [UCT]: 2024-06-30 18:36:36 Age [y:d:h:m:s]: 00:342:00:08:54
Block: 1055660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244440 RingCT/type: yes/0
Extra: 01b8ae6d74f03a6f2f1ed57d9744283438de9ba6ec1ae045de4377bab468928bbc02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4408cdbfce25a184d90ea9df4b87ae4970a61e957748cecf6d7f0d907b18cd7d 0.600000000000 1526065 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": 1055670, "vin": [ { "gen": { "height": 1055660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4408cdbfce25a184d90ea9df4b87ae4970a61e957748cecf6d7f0d907b18cd7d" } } ], "extra": [ 1, 184, 174, 109, 116, 240, 58, 111, 47, 30, 213, 125, 151, 68, 40, 52, 56, 222, 155, 166, 236, 26, 224, 69, 222, 67, 119, 186, 180, 104, 146, 139, 188, 2, 17, 0, 0, 0, 5, 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