← previous blocknext block →recent activity
Analyzing
Block #87,665,299
19 transactions · 16 stateful · 2026-07-14 08:36:59 UTC
Parallelism
84/100
Blocked
19%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,665,299 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w211w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x044844a0…7418
0x34b655…2a6f
4 touches
1 conflict
0x32dfa6a9…12f6
0x34b655…2a6f
4 touches
1 conflict
0x656e0fef…f2a4
0x34b655…2a6f
4 touches
1 conflict
0x659bb236…9438
0x34b655…2a6f
4 touches
1 conflict
0x92e28bd4…72cc
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
3 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity