← previous blocknext block →recent activity
Analyzing
Block #87,667,570
27 transactions · 22 stateful · 2026-07-14 08:52:08 UTC
Parallelism
85/100
Blocked
50%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,667,570 · 27 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
1w02w03w14w07w08w111w012w113w114w115w018w119w222w123w224w325w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x588c5b6a…60d2
0x34b655…2a6f
6 touches
3 conflicts
0x7accd167…4103
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4c188934…158e
0x34b655…2a6f
4 touches
1 conflict
0x536588d3…19c5
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
0x34b655…2a6f
4 touches
1 conflict
0x8247139e…d56e
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 0x588c5b6adb…3060d2
Audit this contract →
← previous block·next block →recent activity