← previous blocknext block →recent activity
Analyzing
Block #99,191,200
21 transactions · 18 stateful · 2026-08-26 00:55:19 UTC
Parallelism
86/100
Blocked
39%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,191,200 · 21 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
1w06w07w18w210w011w112w013w114w219w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c2d19c2…51da
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xfa09be5a…1e79
0x34b655…2a6f
6 touches
3 conflicts
0xeb7ba01b…5f0a
0x065c9d…c394
4 touches
1 conflict
0x0fe9ce4d…1d44
0x34b655…2a6f
4 touches
1 conflict
0x29867567…35b3
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x48b13e5e…3c2a
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 0x3c2d19c21e…2751da
Audit this contract →
← previous block·next block →recent activity