Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3566457e536f490bafbf72f6ef9357b6f19bf14ea6c4566020134451ae3f507

Tx prefix hash: 562c9db825ab8751cf8f50872566415ad1ca0d2d3632af0c75ab2692044e11d6
Tx public key: 48a33990f3f7c8d04e2623a9c2506e8a7ce3c2351780fb657fc757694b552db5
Timestamp: 1697458898 Timestamp [UCT]: 2023-10-16 12:21:38 Age [y:d:h:m:s]: 01:087:18:09:28
Block: 870879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323976 RingCT/type: yes/0
Extra: 0148a33990f3f7c8d04e2623a9c2506e8a7ce3c2351780fb657fc757694b552db502110000000175e3f0e9000000000000000000

1 output(s) for total of 0.798760132000 dcy

stealth address amount amount idx
00: e7d084c92d72f9a7643c4120f5d91f0118b8f2aab203073fcfe98a867961ad38 0.798760132000 1325834 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": 870889, "vin": [ { "gen": { "height": 870879 } } ], "vout": [ { "amount": 798760132, "target": { "key": "e7d084c92d72f9a7643c4120f5d91f0118b8f2aab203073fcfe98a867961ad38" } } ], "extra": [ 1, 72, 163, 57, 144, 243, 247, 200, 208, 78, 38, 35, 169, 194, 80, 110, 138, 124, 227, 194, 53, 23, 128, 251, 101, 127, 199, 87, 105, 75, 85, 45, 181, 2, 17, 0, 0, 0, 1, 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