← previous blocknext block →recent activity
Analyzing
Block #99,170,654
16 transactions · 15 stateful · 2026-08-25 23:11:56 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,170,654 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w18w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8383cd6c…9e62
0x34b655…2a6f
4 touches
1 conflict
0x0b6939da…b459
0x5ef52d…4343
2 touches
1 conflict
0x33450b54…6744
0x188d58…ea8e
2 touches
0 conflicts
0xa5a4bb2c…f2c7
0x188d58…ea8e
2 touches
0 conflicts
0xaecd6ed8…95ad
0x188d58…ea8e
2 touches
0 conflicts
0x0a809ce1…7894
0x34b655…2a6f
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
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity