← previous blocknext block →recent activity
Analyzing
Block #87,703,566
19 transactions · 17 stateful · 2026-07-14 12:52:56 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,703,566 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w08w19w210w311w314w115w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x616c7c23…14e7
0x34b655…2a6f
6 touches
3 conflicts
0xdfc21d7c…e062
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x4755fafb…859b
0x34b655…2a6f
4 touches
1 conflict
0x4de2f250…b472
0x34b655…2a6f
4 touches
1 conflict
0x4f51d069…d0b4
0x34b655…2a6f
4 touches
1 conflict
0x4fc141d9…bb36
0x34b655…2a6f
4 touches
1 conflict
0x5c79a7db…b7aa
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 0x616c7c23a8…3614e7
Audit this contract →
← previous block·next block →recent activity