Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a89e11dddfe9e30d8c7e54ab240f8ecdf516e84702c1d89894969b434504ce68

Tx prefix hash: d68ef0ec376d9bf9d0854238aed439bc1d6b72ff5cf68dcf6fbcf1b3a9570ef0
Tx public key: db88b31a7fe89a07b096fd19db3f247c34d0bdf26acc4997b7cd869aa64a42b9
Timestamp: 1637325280 Timestamp [UCT]: 2021-11-19 12:34:40 Age [y:d:h:m:s]: 03:081:06:10:07
Block: 377601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 836663 RingCT/type: yes/0
Extra: 01db88b31a7fe89a07b096fd19db3f247c34d0bdf26acc4997b7cd869aa64a42b9021100000010d6e4826b000000000000000000

1 output(s) for total of 34.423222311000 dcy

stealth address amount amount idx
00: 53d87d9fb991bdd1404ff7008ad68ff381e6f4b1bf5b1f94d6e65e8d568b9b1a 34.423222311000 763727 of 0

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": 377611, "vin": [ { "gen": { "height": 377601 } } ], "vout": [ { "amount": 34423222311, "target": { "key": "53d87d9fb991bdd1404ff7008ad68ff381e6f4b1bf5b1f94d6e65e8d568b9b1a" } } ], "extra": [ 1, 219, 136, 179, 26, 127, 232, 154, 7, 176, 150, 253, 25, 219, 63, 36, 124, 52, 208, 189, 242, 106, 204, 73, 151, 183, 205, 134, 154, 166, 74, 66, 185, 2, 17, 0, 0, 0, 16, 214, 228, 130, 107, 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