← previous blocknext block →recent activity
Analyzing
Block #87,454,091
11 transactions · 11 stateful · 2026-07-13 09:03:52 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,454,091 · 11 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
2w03w17w08w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd42fdceb…d869
0x34b655…2a6f
4 touches
1 conflict
0xea0fee48…1fab
0x34b655…2a6f
4 touches
1 conflict
0xd42fdceb…d86a
0x34b655…2a6f
4 touches
1 conflict
0xef9cfcf5…1bc0
0x34b655…2a6f
4 touches
1 conflict
0x0b18142d…18bc
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x4e815ddc…2f85
0x34b655…2a6f
4 touches
1 conflict
0x67d8b378…f2f8
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 0xd42fdceb99…57d869
Audit this contract →
← previous block·next block →recent activity