← previous blocknext block →recent activity
Analyzing
Block #99,624,787
20 transactions · 18 stateful · 2026-08-27 13:24:45 UTC
Parallelism
55/100
Blocked
50%
Avg conflicts / tx
1.6
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #99,624,787 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w38w49w512w618w719w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaf5fe80…1ffc
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x35653f1a…b03c
0x34b655…2a6f
6 touches
3 conflicts
0xb0caf05b…3432
0x34b655…2a6f
6 touches
3 conflicts
0xa6b48d6e…0705
0x34b655…2a6f
4 touches
1 conflict
0x014e90b3…470f
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
15 conflicts on slot 0xfaf5fe80ab…a71ffc
Audit this contract →
← previous block·next block →recent activity