← previous blocknext block →recent activity
Analyzing
Block #87,620,642
28 transactions · 24 stateful · 2026-07-14 03:38:30 UTC
Parallelism
68/100
Blocked
63%
Avg conflicts / tx
1.71
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #87,620,642 · 28 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w38w49w510w611w712w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x40b18770…e631
0x34b655…2a6f
14 touches
21 conflicts
0x49f75237…44f4
0x34b655…2a6f
14 touches
21 conflicts
0x2cad7826…7a77
0x34b655…2a6f
14 touches
21 conflicts
0x7bc81c3e…54a2
0x34b655…2a6f
14 touches
21 conflicts
0x8d68898d…ab1d
0x34b655…2a6f
14 touches
21 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
14 touches
21 conflicts
0xd19c9d38…b459
0x34b655…2a6f
14 touches
21 conflicts
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity