← previous blocknext block →recent activity
Analyzing
Block #99,879,447
20 transactions · 18 stateful · 2026-08-28 10:52:56 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,879,447 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w111w114w215w318w019w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x272e6316…bbe8
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x74c7e34f…daae
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xa9614592…4fc2
0x40c49f…2af0
4 touches
1 conflict
0xd08db6ee…a943
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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
6 conflicts on slot 0x272e631653…94bbe8
Audit this contract →
← previous block·next block →recent activity