← previous blocknext block →recent activity
Analyzing
Block #88,806,111
12 transactions · 11 stateful · 2026-07-19 15:49:38 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,806,111 · 12 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
3w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08e72cb0…d3aa
0x34b655…2a6f
4 touches
1 conflict
0x2d1bfc5e…dbf9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0x58bce2bb…a259
0x34b655…2a6f
4 touches
1 conflict
0x59a54ff4…d21b
0x34b655…2a6f
4 touches
1 conflict
0x5af84880…55de
0x34b655…2a6f
4 touches
1 conflict
0x6d94d7d6…6ed4
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
1 conflict on slot 0x08e72cb000…3ed3aa
Audit this contract →
← previous block·next block →recent activity