← previous blocknext block →recent activity
Analyzing
Block #88,183,821
22 transactions · 18 stateful · 2026-07-16 18:26:08 UTC
Parallelism
64/100
Blocked
44%
Avg conflicts / tx
0.77
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #88,183,821 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w17w28w39w413w515w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c46fde6…d6a0
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x9001f549…089d
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x70e3da66…674a
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 0x7c46fde6b8…2fd6a0
Audit this contract →
← previous block·next block →recent activity