← previous blocknext block →recent activity
Analyzing
Block #87,734,498
20 transactions · 17 stateful · 2026-07-14 16:20:03 UTC
Parallelism
60/100
Blocked
41%
Avg conflicts / tx
1.4
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,734,498 · 20 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
5w06w17w28w39w411w012w513w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa55c4598…2988
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0xed59b1cd…8509
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x58620f29…db5a
0x34b655…2a6f
8 touches
6 conflicts
0xef70190e…6150
0x34b655…2a6f
8 touches
6 conflicts
0x49f75237…44f4
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0xa55c45989b…e52988
Audit this contract →
← previous block·next block →recent activity