← previous blocknext block →recent activity
Analyzing
Block #87,293,014
30 transactions · 27 stateful · 2026-07-12 15:06:44 UTC
Parallelism
80/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,293,014 · 30 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
11w012w115w016w120w221w122w323w227w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e166a45…98a7
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xa832fdf3…64b4
0x34b655…2a6f
6 touches
3 conflicts
0x3c7908ed…47c8
0x34b655…2a6f
4 touches
1 conflict
0x3ef0952c…762d
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x940bc534…1219
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 0x1e166a4530…8298a7
Audit this contract →
← previous block·next block →recent activity