← previous blocknext block →recent activity
Analyzing
Block #87,257,328
13 transactions · 12 stateful · 2026-07-12 11:08:07 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,257,328 · 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
1w03w04w06w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52163873…f09f
0x34b655…2a6f
4 touches
1 conflict
0xebd8c9b0…2ba6
0x34b655…2a6f
4 touches
1 conflict
0xcc13c07b…d7cc
0x34b655…2a6f
4 touches
1 conflict
0xb207488f…fca0
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x8b8a50e1…b5dc
0x34b655…2a6f
4 touches
1 conflict
0x39669b27…cc22
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 0x5216387342…22f09f
Audit this contract →
← previous block·next block →recent activity