← previous blocknext block →recent activity
Analyzing
Block #87,753,888
20 transactions · 20 stateful · 2026-07-14 18:29:47 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,753,888 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w010w111w013w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x648bb928…97f2
0x34b655…2a6f
6 touches
3 conflicts
0x309e07fc…9a08
0x34b655…2a6f
4 touches
1 conflict
0x3244bc68…5263
0x34b655…2a6f
4 touches
1 conflict
0x3a8dad6e…4fe6
0x34b655…2a6f
4 touches
1 conflict
0x3bca5b95…9ee9
0x34b655…2a6f
4 touches
1 conflict
0x3e8b3a49…53ee
0x34b655…2a6f
4 touches
1 conflict
0x48260180…a411
0x34b655…2a6f
4 touches
1 conflict
0x48260180…a412
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
3 conflicts on slot 0x648bb9281b…e597f2
Audit this contract →
← previous block·next block →recent activity