← previous blocknext block →recent activity
Analyzing
Block #83,401,156
19 transactions · 12 stateful · 2026-06-24 14:18:59 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,401,156 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w010w111w212w313w014w118w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x9c7571b3…9605
0x34b655…2a6f
6 touches
3 conflicts
0xff107718…55e9
0x34b655…2a6f
6 touches
3 conflicts
0xa1571d54…ae41
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x3c9bce0e…0440
0x34b655…2a6f
4 touches
2 conflicts
0x495dbfef…6da8
0x34b655…2a6f
4 touches
1 conflict
0x5396d712…a139
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity