← previous blocknext block →recent activity
Analyzing
Block #83,483,163
28 transactions · 21 stateful · 2026-06-24 23:26:38 UTC
Parallelism
75/100
Blocked
67%
Avg conflicts / tx
1.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,483,163 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w17w29w310w011w112w213w314w415w516w617w421w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0x731e6d82…2883
0x065c9d…c394
8 touches
6 conflicts
0x05289bd6…9ab4
0x34b655…2a6f
6 touches
3 conflicts
0x13c5b486…d41e
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xe783dfa4…5493
0x1b6862…e19c
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity