Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 768cfa0ff9a2a501b2019109ec99b7b2e8def9b0cb29c457fbdf5eab0dcfe95e

Tx prefix hash: 1ea8a744ecc5a81241275cbd6bdf054e5f0d4bcd6a2e5ad55a3bcb0685b4daee
Tx public key: e2ae3f3908dffcc7217f577cad84d61397363fb36008d3e175a94c2ed2d93dee
Timestamp: 1665560297 Timestamp [UCT]: 2022-10-12 07:38:17 Age [y:d:h:m:s]: 02:180:04:08:31
Block: 607350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 650335 RingCT/type: yes/0
Extra: 01e2ae3f3908dffcc7217f577cad84d61397363fb36008d3e175a94c2ed2d93dee02110000000d71bd5189000000000000000000

1 output(s) for total of 5.964820460000 dcy

stealth address amount amount idx
00: d9a6a9a04a20827030fbbe2d7d1aba7371a95c5f9a9e6a98f4dad332eab1d5cc 5.964820460000 1043974 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": 607360, "vin": [ { "gen": { "height": 607350 } } ], "vout": [ { "amount": 5964820460, "target": { "key": "d9a6a9a04a20827030fbbe2d7d1aba7371a95c5f9a9e6a98f4dad332eab1d5cc" } } ], "extra": [ 1, 226, 174, 63, 57, 8, 223, 252, 199, 33, 127, 87, 124, 173, 132, 214, 19, 151, 54, 63, 179, 96, 8, 211, 225, 117, 169, 76, 46, 210, 217, 61, 238, 2, 17, 0, 0, 0, 13, 113, 189, 81, 137, 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