← previous blocknext block →recent activity
Analyzing
Block #83,398,033
20 transactions · 18 stateful · 2026-06-24 13:58:06 UTC
Parallelism
60/100
Blocked
56%
Avg conflicts / tx
1.7
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,398,033 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w38w49w510w611w712w119w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0xb6632320…a3ce
0x34b655…2a6f
6 touches
3 conflicts
0x7d68b808…c6e3
0x34b655…2a6f
6 touches
3 conflicts
0xa51c97e1…6b55
0x34b655…2a6f
6 touches
3 conflicts
0xe283e878…7262
0x34b655…2a6f
6 touches
3 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
6 touches
3 conflicts
0xa1571d54…ae41
0x34b655…2a6f
4 touches
1 conflict
0xc56d6548…50a4
0x34b655…2a6f
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
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity