Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9946cad7f4b42dc1ac942ff5cd37da8ff762a8e5d8ddf4518c5dd4ab57108d9f

Tx prefix hash: bfd98197decc71824200aa3a604e07dd32277cae25287e4021478400353f2842
Tx public key: fa426d57c0fcf8358730da8d9a7e94b671213fc3b8c92c686c2690f72eddd2a4
Timestamp: 1659551764 Timestamp [UCT]: 2022-08-03 18:36:04 Age [y:d:h:m:s]: 03:089:20:07:47
Block: 557993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 844000 RingCT/type: yes/0
Extra: 01fa426d57c0fcf8358730da8d9a7e94b671213fc3b8c92c686c2690f72eddd2a402110000000d6570b1ef000000000000000000

1 output(s) for total of 8.692359460000 dcy

stealth address amount amount idx
00: a3426f900fa3a97068c7efa3a3a4eeb219f8409736689c9f19f94c6f6faed039 8.692359460000 990045 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": 558003, "vin": [ { "gen": { "height": 557993 } } ], "vout": [ { "amount": 8692359460, "target": { "key": "a3426f900fa3a97068c7efa3a3a4eeb219f8409736689c9f19f94c6f6faed039" } } ], "extra": [ 1, 250, 66, 109, 87, 192, 252, 248, 53, 135, 48, 218, 141, 154, 126, 148, 182, 113, 33, 63, 195, 184, 201, 44, 104, 108, 38, 144, 247, 46, 221, 210, 164, 2, 17, 0, 0, 0, 13, 101, 112, 177, 239, 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