← previous blocknext block →recent activity
Analyzing
Block #88,184,123
10 transactions · 9 stateful · 2026-07-16 18:28:10 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,184,123 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16dce2e7…6f05
0x34b655…2a6f
6 touches
3 conflicts
0x478e6e08…83bf
0x34b655…2a6f
4 touches
1 conflict
0x82f08cb8…4d94
0x34b655…2a6f
4 touches
1 conflict
0x82f08cb8…4d95
0x34b655…2a6f
4 touches
1 conflict
0xafa812b6…232e
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
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 0x16dce2e7df…1b6f05
Audit this contract →
← previous block·next block →recent activity