← previous blocknext block →recent activity
Analyzing
Block #99,874,350
24 transactions · 22 stateful · 2026-08-28 10:27:15 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,874,350 · 24 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
1w02w110w011w112w013w114w215w317w218w321w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8017713…e28b
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
6 touches
3 conflicts
0x0d03bddb…6658
0x34b655…2a6f
6 touches
3 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x52cef1b0…0e4e
0x34b655…2a6f
4 touches
1 conflict
0x5a02cdfe…f29c
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
6 conflicts on slot 0xf8017713ec…5be28b
Audit this contract →
← previous block·next block →recent activity