Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e764e2f50b8896ec0a8cd2c3b0cd1504857e8545f58020cdba7d0d557f7643e

Tx prefix hash: a8085c13b647699bf2a32699ca0564662f6fda26a79729d3a9991428b69d83a1
Tx public key: 1e599f2b4935d69e259845e7a4932fbf4b373fb0ff1df4b510021fa9bdce76c5
Timestamp: 1682201251 Timestamp [UCT]: 2023-04-22 22:07:31 Age [y:d:h:m:s]: 02:170:10:53:06
Block: 744431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 641623 RingCT/type: yes/0
Extra: 011e599f2b4935d69e259845e7a4932fbf4b373fb0ff1df4b510021fa9bdce76c502110000000275e3f0e9000000000000000000

1 output(s) for total of 2.096000010000 dcy

stealth address amount amount idx
00: 8e1f0c3fb24c33125724888c4c5e0c295295dcb46582acf1af1db2c66398ac16 2.096000010000 1191750 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": 744441, "vin": [ { "gen": { "height": 744431 } } ], "vout": [ { "amount": 2096000010, "target": { "key": "8e1f0c3fb24c33125724888c4c5e0c295295dcb46582acf1af1db2c66398ac16" } } ], "extra": [ 1, 30, 89, 159, 43, 73, 53, 214, 158, 37, 152, 69, 231, 164, 147, 47, 191, 75, 55, 63, 176, 255, 29, 244, 181, 16, 2, 31, 169, 189, 206, 118, 197, 2, 17, 0, 0, 0, 2, 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