← previous blocknext block →recent activity
Analyzing
Block #87,499,162
33 transactions · 25 stateful · 2026-07-13 14:05:16 UTC
Parallelism
85/100
Blocked
48%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,499,162 · 33 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
1w02w03w14w29w010w115w116w117w218w321w222w323w324w427w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93ef53c7…f210
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
6 touches
3 conflicts
0x614dcfbb…2f4e
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
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 0x93ef53c71a…76f210
Audit this contract →
← previous block·next block →recent activity