← previous blocknext block →recent activity
Analyzing
Block #87,490,516
22 transactions · 17 stateful · 2026-07-13 13:07:25 UTC
Parallelism
82/100
Blocked
35%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,490,516 · 22 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
7w08w110w011w115w116w217w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96bfa04d…d06b
0x34b655…2a6f
6 touches
3 conflicts
0xb9266685…8b1d
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x23fed4a9…f923
0x34b655…2a6f
4 touches
1 conflict
0x23fed4a9…f924
0x34b655…2a6f
4 touches
1 conflict
0x375e887b…a361
0x34b655…2a6f
4 touches
1 conflict
0x375e887b…a362
0x34b655…2a6f
4 touches
1 conflict
0x5e2ddc8a…b7a5
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
3 conflicts on slot 0x96bfa04d52…3ed06b
Audit this contract →
← previous block·next block →recent activity