← previous blocknext block →recent activity
Analyzing
Block #87,709,762
16 transactions · 13 stateful · 2026-07-14 13:34:26 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,709,762 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x030bd256…c5c3
0x34b655…2a6f
4 touches
1 conflict
0x0a7a49dc…a295
0x34b655…2a6f
4 touches
1 conflict
0x197e2da8…f1f4
0x34b655…2a6f
4 touches
1 conflict
0x2ecf1f31…9a68
0x34b655…2a6f
4 touches
1 conflict
0x3b679ba3…b050
0x34b655…2a6f
4 touches
1 conflict
0x402e43c2…7ed0
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity