← previous blocknext block →recent activity
Analyzing
Block #87,576,271
8 transactions · 8 stateful · 2026-07-13 22:41:47 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,576,271 · 8 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
2w03w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x558fd353…1c6b
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x043fd28f…ca21
0x34b655…2a6f
2 touches
0 conflicts
0x0ae9d2df…f787
0x34b655…2a6f
2 touches
0 conflicts
0x0ae9d2df…f788
0x34b655…2a6f
2 touches
0 conflicts
0x0c15f714…46ab
0x34b655…2a6f
2 touches
0 conflicts
0x8486462c…1f6c
0x34b655…2a6f
2 touches
0 conflicts
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 0x558fd353c6…4b1c6b
Audit this contract →
← previous block·next block →recent activity