← previous blocknext block →recent activity
Analyzing
Block #87,643,163
13 transactions · 9 stateful · 2026-07-14 06:09:04 UTC
Parallelism
85/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,643,163 · 13 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
3w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x4f4a7ac3…021c
0x34b655…2a6f
4 touches
1 conflict
0x06c2c8c1…c2a9
0x34b655…2a6f
2 touches
0 conflicts
0x11d629eb…bcd9
0x34b655…2a6f
2 touches
0 conflicts
0x2ae834f7…a036
0x34b655…2a6f
2 touches
0 conflicts
0x2b2cf495…1c6f
0x34b655…2a6f
2 touches
0 conflicts
0x2b2cf495…1c70
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity