← previous blocknext block →recent activity
Analyzing
Block #87,352,211
14 transactions · 14 stateful · 2026-07-12 21:42:31 UTC
Parallelism
86/100
Blocked
7%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,352,211 · 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
1w02w06w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d105005…3cc9
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0xc03846bb…73b3
0x34b655…2a6f
4 touches
1 conflict
0x0be747d5…22e1
0x34b655…2a6f
4 touches
1 conflict
0x2328941c…84d3
0x34b655…2a6f
4 touches
1 conflict
0xf6e96689…496a
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
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 0x6d105005a2…ba3cc9
Audit this contract →
← previous block·next block →recent activity