← previous blocknext block →recent activity
Analyzing
Block #87,661,267
17 transactions · 13 stateful · 2026-07-14 08:10:00 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,661,267 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x64687417…8d60
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x04c1786f…3ee6
0x34b655…2a6f
2 touches
0 conflicts
0x099dde1a…3e64
0x34b655…2a6f
2 touches
0 conflicts
0x0dcb313d…7073
0x34b655…2a6f
2 touches
0 conflicts
0x11299a8d…3937
0x34b655…2a6f
2 touches
0 conflicts
0x117cb8ea…a1dc
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity