← previous blocknext block →recent activity
Analyzing
Block #87,731,422
13 transactions · 12 stateful · 2026-07-14 15:59:29 UTC
Parallelism
46/100
Blocked
58%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,731,422 · 13 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w09w610w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80fd3987…2314
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xa55c4598…2988
0x34b655…2a6f
6 touches
3 conflicts
0x255ba9f3…396d
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0x64a058c6…74a1
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
6 conflicts on slot 0x80fd398747…852314
Audit this contract →
← previous block·next block →recent activity