← previous blocknext block →recent activity
Analyzing
Block #87,666,942
14 transactions · 12 stateful · 2026-07-14 08:47:56 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,666,942 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04f4909f…6357
0x34b655…2a6f
4 touches
1 conflict
0x0a6af9b9…e844
0x34b655…2a6f
4 touches
1 conflict
0x0d55d89d…a4ec
0x34b655…2a6f
4 touches
1 conflict
0x1487893e…4055
0x34b655…2a6f
4 touches
1 conflict
0x1a017137…af9f
0x34b655…2a6f
4 touches
1 conflict
0x45db1a5d…eab1
0x34b655…2a6f
4 touches
1 conflict
0x56ea7d7d…445a
0x34b655…2a6f
4 touches
1 conflict
0x606df5d3…0960
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
1 conflict on slot 0x04f4909fbe…1b6357
Audit this contract →
← previous block·next block →recent activity