← previous blocknext block →recent activity
Analyzing
Block #87,668,379
18 transactions · 15 stateful · 2026-07-14 08:57:33 UTC
Parallelism
78/100
Blocked
27%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,668,379 · 18 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
2w03w17w08w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x23ea6729…10b6
0x34b655…2a6f
4 touches
1 conflict
0x46a7d766…9797
0x34b655…2a6f
4 touches
1 conflict
0x588c5b6a…60d2
0x34b655…2a6f
4 touches
1 conflict
0x597cad45…e7bf
0x34b655…2a6f
4 touches
1 conflict
0x6529e3e7…e10c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
3 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity