← previous blocknext block →recent activity
Analyzing
Block #87,487,883
11 transactions · 11 stateful · 2026-07-13 12:49:48 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.82
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,487,883 · 11 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
2w03w16w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9266685…8b1d
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x96bfa04d…d06b
0x34b655…2a6f
6 touches
3 conflicts
0x7252311d…d8cf
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x4f461bcd…ef71
0x34b655…2a6f
6 touches
3 conflicts
0x3a0ed747…70c7
0x34b655…2a6f
4 touches
1 conflict
0x3d4c0233…20a5
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 0xb92666855b…228b1d
Audit this contract →
← previous block·next block →recent activity