← previous blocknext block →recent activity
Analyzing
Block #99,618,361
17 transactions · 17 stateful · 2026-08-27 12:51:53 UTC
Parallelism
59/100
Blocked
53%
Avg conflicts / tx
1.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,618,361 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w27w38w411w512w615w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xfbbb109c…679b
0x34b655…2a6f
10 touches
10 conflicts
0x1bb1ae15…02fe
0x34b655…2a6f
10 touches
10 conflicts
0x39ccd26a…4654
0x34b655…2a6f
10 touches
10 conflicts
0xf195ad96…e0c3
0x34b655…2a6f
8 touches
6 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
6 touches
3 conflicts
0x939cdd56…00c8
0x34b655…2a6f
6 touches
3 conflicts
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity