← previous blocknext block →recent activity
Analyzing
Block #87,691,838
16 transactions · 15 stateful · 2026-07-14 11:34:19 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,691,838 · 16 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
1w03w04w17w18w29w312w413w515w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x836544ae…79e6
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x0b234df0…aee3
0x34b655…2a6f
6 touches
3 conflicts
0x013f8235…a848
0x34b655…2a6f
4 touches
1 conflict
0x9b36f19f…fa5a
0x34b655…2a6f
4 touches
1 conflict
0xdcb19a49…ffd5
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 0x836544ae2a…5879e6
Audit this contract →
← previous block·next block →recent activity