← previous blocknext block →recent activity
Analyzing
Block #87,063,499
12 transactions · 12 stateful · 2026-07-11 13:31:52 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,063,499 · 12 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
2w03w06w17w210w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56b5f5c0…a3ad
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x1bde87f2…0843
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x4b2b1640…1bb8
0x34b655…2a6f
4 touches
1 conflict
0x4c5f596d…5b4c
0x34b655…2a6f
4 touches
1 conflict
0x79384ae7…b8b9
0x34b655…2a6f
4 touches
1 conflict
0x81336c06…2daf
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
6 conflicts on slot 0x56b5f5c03e…07a3ad
Audit this contract →
← previous block·next block →recent activity