Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99290f9e9c2c1f4a8873aa32b4877d679fc5556444c95c76294b50fae00e91ca

Tx prefix hash: 1055316316f07323c82c91ac337d9967e8b9800bfdd09959c7096bb43735307e
Tx public key: 5a07713dca6877e88ec0a080bf3d3b441e48fcb59f2e0b74d0550379f00620b7
Timestamp: 1697175648 Timestamp [UCT]: 2023-10-13 05:40:48 Age [y:d:h:m:s]: 01:099:05:48:28
Block: 868534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332145 RingCT/type: yes/0
Extra: 015a07713dca6877e88ec0a080bf3d3b441e48fcb59f2e0b74d0550379f00620b702110000000333af99f4000000000000000000

1 output(s) for total of 0.813179351000 dcy

stealth address amount amount idx
00: 7dcb9d0d82a1a193809e7f0694043a17f6cc1a26eab680b86e65d2a204d72e17 0.813179351000 1323347 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": 868544, "vin": [ { "gen": { "height": 868534 } } ], "vout": [ { "amount": 813179351, "target": { "key": "7dcb9d0d82a1a193809e7f0694043a17f6cc1a26eab680b86e65d2a204d72e17" } } ], "extra": [ 1, 90, 7, 113, 61, 202, 104, 119, 232, 142, 192, 160, 128, 191, 61, 59, 68, 30, 72, 252, 181, 159, 46, 11, 116, 208, 85, 3, 121, 240, 6, 32, 183, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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