← previous blocknext block →recent activity
Analyzing
Block #87,498,429
19 transactions · 16 stateful · 2026-07-13 14:00:22 UTC
Parallelism
58/100
Blocked
56%
Avg conflicts / tx
1.05
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,498,429 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w18w29w311w312w413w514w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x17b720f5…ad7a
0x34b655…2a6f
8 touches
6 conflicts
0x01e39429…f244
0x34b655…2a6f
6 touches
3 conflicts
0x1e6e9104…f143
0x34b655…2a6f
6 touches
3 conflicts
0xab96ac84…a512
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
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
10 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity