← previous blocknext block →recent activity
Analyzing
Block #87,792,146
17 transactions · 17 stateful · 2026-07-14 22:45:43 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,792,146 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w010w111w012w213w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d989c17…e984
0x34b655…2a6f
6 touches
3 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x04a566e1…26f3
0x34b655…2a6f
4 touches
1 conflict
0x1f644d6b…368c
0x34b655…2a6f
4 touches
1 conflict
0x26824212…7064
0x34b655…2a6f
4 touches
1 conflict
0x346e6e22…8deb
0x34b655…2a6f
4 touches
1 conflict
0x3ce18150…5820
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 0x8d989c177f…b7e984
Audit this contract →
← previous block·next block →recent activity