Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f769f249cf4a2efa4aecb2ec6a208dbc63ecd67ee0fb1c5c4fd9f47b108c1ef

Tx prefix hash: 176937b44dbd1b83a05f0278f8e0cc24305ce59e1f4fa4c36f0dbc8b23d477c7
Tx public key: d48b53e4ebf353bbf844a23a2ebe2138efa1c6e6f8133eaa878dd1e39493a174
Timestamp: 1690003799 Timestamp [UCT]: 2023-07-22 05:29:59 Age [y:d:h:m:s]: 01:253:08:48:59
Block: 809138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442175 RingCT/type: yes/0
Extra: 01d48b53e4ebf353bbf844a23a2ebe2138efa1c6e6f8133eaa878dd1e39493a17402110000000675e3f0e9000000000000000000

1 output(s) for total of 1.279351944000 dcy

stealth address amount amount idx
00: 2472a65dcda052f9c907d6b5c58f17bd26886101a2ed583f0c3135f68d36a6ed 1.279351944000 1260737 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": 809148, "vin": [ { "gen": { "height": 809138 } } ], "vout": [ { "amount": 1279351944, "target": { "key": "2472a65dcda052f9c907d6b5c58f17bd26886101a2ed583f0c3135f68d36a6ed" } } ], "extra": [ 1, 212, 139, 83, 228, 235, 243, 83, 187, 248, 68, 162, 58, 46, 190, 33, 56, 239, 161, 198, 230, 248, 19, 62, 170, 135, 141, 209, 227, 148, 147, 161, 116, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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