← previous blocknext block →recent activity
Analyzing
Block #87,053,254
18 transactions · 16 stateful · 2026-07-11 12:23:25 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,053,254 · 18 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
1w02w16w07w18w29w312w013w014w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x9199a85a…acd9
0x34b655…2a6f
8 touches
6 conflicts
0xf5042875…9a93
0x34b655…2a6f
8 touches
6 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xc6ce2d18…5786
0x34b655…2a6f
6 touches
3 conflicts
0xd1c5aeea…ee0a
0x34b655…2a6f
6 touches
3 conflicts
0xdb3937e8…23cb
0x34b655…2a6f
6 touches
3 conflicts
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity