← previous blocknext block →recent activity
Analyzing
Block #87,640,213
14 transactions · 11 stateful · 2026-07-14 05:49:23 UTC
Parallelism
71/100
Blocked
27%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,640,213 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d66de6b…202b
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x0f15f74f…8d72
0x34b655…2a6f
4 touches
1 conflict
0x14c5407b…4a40
0x34b655…2a6f
4 touches
1 conflict
0x1737ef68…1e55
0x34b655…2a6f
4 touches
1 conflict
0x1bb2616f…b731
0x34b655…2a6f
4 touches
1 conflict
0x1bb2616f…b732
0x34b655…2a6f
4 touches
1 conflict
0x26054cbe…47df
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 0x4d66de6b96…2e202b
Audit this contract →
← previous block·next block →recent activity