← previous blocknext block →recent activity
Analyzing
Block #99,813,414
17 transactions · 17 stateful · 2026-08-28 05:19:24 UTC
Parallelism
47/100
Blocked
53%
Avg conflicts / tx
2.18
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #99,813,414 · 17 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w19w110w211w312w413w514w615w716w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
18 touches
36 conflicts
0x92385428…6941
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x886db264…846e
0x34b655…2a6f
16 touches
28 conflicts
0x230d0904…a656
0x34b655…2a6f
10 touches
10 conflicts
0x7e59f6d5…68f0
0x34b655…2a6f
7 touches
6 conflicts
0xadc4ee2a…56e4
0x34b655…2a6f
6 touches
3 conflicts
0x3ed49969…0ed7
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
36 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity