Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7ac54cb2926cb22d0b3fd8406fe6cb53e1a4dfda6417309b3e94327033c36ed

Tx prefix hash: 878f5d54ce12111623d19b8cd1ef4fa6ebf9f11da7c146c40317ccd9dfa3879b
Tx public key: 543c35dec3528d9d04af17d18dbdc18138537c5aed30c231cfc1dc9dd1df8e69
Timestamp: 1722296105 Timestamp [UCT]: 2024-07-29 23:35:05 Age [y:d:h:m:s]: 00:246:03:28:31
Block: 1076583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175813 RingCT/type: yes/0
Extra: 01543c35dec3528d9d04af17d18dbdc18138537c5aed30c231cfc1dc9dd1df8e6902110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87a2f8cf438c226898ffe051976f701586042ae86fd4deb5ebd7b949146623ee 0.600000000000 1549122 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": 1076593, "vin": [ { "gen": { "height": 1076583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87a2f8cf438c226898ffe051976f701586042ae86fd4deb5ebd7b949146623ee" } } ], "extra": [ 1, 84, 60, 53, 222, 195, 82, 141, 157, 4, 175, 23, 209, 141, 189, 193, 129, 56, 83, 124, 90, 237, 48, 194, 49, 207, 193, 220, 157, 209, 223, 142, 105, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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