← previous blocknext block →recent activity
Analyzing
Block #87,640,931
14 transactions · 12 stateful · 2026-07-14 05:54:10 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,640,931 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xcdd32c46…e107
0x34b655…2a6f
6 touches
3 conflicts
0x59c89f2b…2f10
0x34b655…2a6f
6 touches
3 conflicts
0x0d151fcc…9630
0x34b655…2a6f
4 touches
1 conflict
0x0d151fcc…9631
0x34b655…2a6f
4 touches
1 conflict
0x24f6d4ca…c33b
0x34b655…2a6f
4 touches
1 conflict
0x41a69a83…eed4
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity