Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80bfee3bd0c335a2950d6721da2622351bbe8cf737ffcd94e8f9d61f0001f952

Tx prefix hash: 3f7a2a62effcd064f2ca859e63765f47af50729c0cd2565d483b0508ea8cdfb7
Tx public key: 55b6c682c8037bbd18d2809ae861af5f85acf267f75ed93f0ae13897ca049419
Timestamp: 1725450001 Timestamp [UCT]: 2024-09-04 11:40:01 Age [y:d:h:m:s]: 00:263:05:39:17
Block: 1102746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188014 RingCT/type: yes/0
Extra: 0155b6c682c8037bbd18d2809ae861af5f85acf267f75ed93f0ae13897ca04941902110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bca3ec32a3df83ffb4d6e3a409c51ef2a389d7b8e94e39129b4878bd89f2d8b4 0.600000000000 1579301 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": 1102756, "vin": [ { "gen": { "height": 1102746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bca3ec32a3df83ffb4d6e3a409c51ef2a389d7b8e94e39129b4878bd89f2d8b4" } } ], "extra": [ 1, 85, 182, 198, 130, 200, 3, 123, 189, 24, 210, 128, 154, 232, 97, 175, 95, 133, 172, 242, 103, 247, 94, 217, 63, 10, 225, 56, 151, 202, 4, 148, 25, 2, 17, 0, 0, 0, 2, 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