← previous blocknext block →recent activity
Analyzing
Block #87,575,928
21 transactions · 18 stateful · 2026-07-13 22:39:29 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,575,928 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w09w111w012w215w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68d9d4e4…91b6
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0x33dd7258…dc93
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x884dd0f3…2af0
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 0x68d9d4e48b…0391b6
Audit this contract →
← previous block·next block →recent activity