← previous blocknext block →recent activity
Analyzing
Block #99,853,810
13 transactions · 12 stateful · 2026-08-28 08:43:38 UTC
Parallelism
77/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,853,810 · 13 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
4w05w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b50b454…614a
0x34b655…2a6f
6 touches
3 conflicts
0x91cdfdeb…7feb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe108b282…58b3
0x34b655…2a6f
4 touches
1 conflict
0x0ff5aca0…9c1e
0x065c9d…c394
2 touches
0 conflicts
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0x892daf6e…48d8
0x065c9d…c394
2 touches
0 conflicts
0x8ff0c403…d04c
0x065c9d…c394
2 touches
0 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
3 conflicts on slot 0x5b50b45464…a3614a
Audit this contract →
← previous block·next block →recent activity