← previous blocknext block →recent activity
Analyzing
Block #87,263,885
11 transactions · 9 stateful · 2026-07-12 11:51:55 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,263,885 · 11 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
4w05w06w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf76c239e…39ee
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xc50ac7d4…e964
0x34b655…2a6f
4 touches
1 conflict
0xce6e660b…8d53
0x34b655…2a6f
4 touches
1 conflict
0x0f15f74f…8d71
0x34b655…2a6f
4 touches
1 conflict
0x0f15f74f…8d72
0x34b655…2a6f
4 touches
1 conflict
0x1737ef68…1e55
0x34b655…2a6f
4 touches
1 conflict
0x3d22c439…de6d
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
1 conflict on slot 0xf76c239e13…6c39ee
Audit this contract →
← previous block·next block →recent activity