← previous blocknext block →recent activity
Analyzing
Block #87,729,500
20 transactions · 18 stateful · 2026-07-14 15:46:38 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,729,500 · 20 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
3w04w05w16w27w39w010w111w214w015w317w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74fd0a9b…3aaa
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x9eb155db…f714
0x34b655…2a6f
8 touches
6 conflicts
0x0ba865dd…a249
0x34b655…2a6f
8 touches
6 conflicts
0x78346476…4311
0x34b655…2a6f
6 touches
3 conflicts
0x44d214fe…4f5e
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x74fd0a9bd1…ea3aaa
Audit this contract →
← previous block·next block →recent activity