← previous blocknext block →recent activity
Analyzing
Block #99,879,304
21 transactions · 20 stateful · 2026-08-28 10:52:13 UTC
Parallelism
67/100
Blocked
60%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,879,304 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w08w19w211w312w013w114w215w317w418w519w320w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xc16e646d…4fb0
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x4a41da47…379c
0x34b655…2a6f
8 touches
6 conflicts
0xc0164b20…4db5
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x272e6316…bbe8
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity