← previous blocknext block →recent activity
Analyzing
Block #99,368,828
11 transactions · 11 stateful · 2026-08-26 15:49:16 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.55
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,368,828 · 11 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
2w03w14w26w17w28w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4dc3591…b669
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf8e6479f…f193
0x34b655…2a6f
4 touches
1 conflict
0x81ca8c9e…28cb
0x34b655…2a6f
4 touches
1 conflict
0x9de538e5…7632
0x34b655…2a6f
4 touches
1 conflict
0x9de538e5…7633
0x34b655…2a6f
4 touches
1 conflict
0xc10b903d…2f54
0x34b655…2a6f
4 touches
1 conflict
0xd689a6a5…0d01
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 0xb4dc35918f…85b669
Audit this contract →
← previous block·next block →recent activity