← previous blocknext block →recent activity
Analyzing
Block #87,628,014
24 transactions · 21 stateful · 2026-07-14 04:27:51 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,628,014 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w06w17w28w310w111w215w316w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08330b36…ae29
0x34b655…2a6f
12 touches
15 conflicts
0x43bc2389…898f
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x49f75237…44f4
0x34b655…2a6f
8 touches
6 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x2697123c…8526
0x34b655…2a6f
8 touches
6 conflicts
0x4560e5a8…b741
0x34b655…2a6f
8 touches
6 conflicts
0xd19c9d38…b459
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 0x08330b3687…a7ae29
Audit this contract →
← previous block·next block →recent activity