Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e15eb34ede28d43479e55e22bda52832024e407da201e37a82725d4e2606e5fb

Tx prefix hash: 4d00a9ee9fbc7ef98203850ecd09d61ee32a633cd65efd95f6318e8af1c73c62
Tx public key: 8682775f13fc80d321518b3dbd917717d0b8264cbb8f82c41a93a08c8c7b6351
Timestamp: 1697169996 Timestamp [UCT]: 2023-10-13 04:06:36 Age [y:d:h:m:s]: 01:202:13:59:08
Block: 868486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405837 RingCT/type: yes/0
Extra: 018682775f13fc80d321518b3dbd917717d0b8264cbb8f82c41a93a08c8c7b635102110000001075e3f0e9000000000000000000

1 output(s) for total of 0.813477201000 dcy

stealth address amount amount idx
00: 7991eae8933beacf0e96eead4955f2070f8b3b0dce44603c00c4b276fe60b601 0.813477201000 1323297 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": 868496, "vin": [ { "gen": { "height": 868486 } } ], "vout": [ { "amount": 813477201, "target": { "key": "7991eae8933beacf0e96eead4955f2070f8b3b0dce44603c00c4b276fe60b601" } } ], "extra": [ 1, 134, 130, 119, 95, 19, 252, 128, 211, 33, 81, 139, 61, 189, 145, 119, 23, 208, 184, 38, 76, 187, 143, 130, 196, 26, 147, 160, 140, 140, 123, 99, 81, 2, 17, 0, 0, 0, 16, 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