← previous blocknext block →recent activity
Analyzing
Block #99,279,296
24 transactions · 23 stateful · 2026-08-26 08:18:36 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,279,296 · 24 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
1w04w15w16w211w312w414w015w116w417w018w119w222w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71fad9ce…c11f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xc8ab31f9…8ce9
0xa6afd3…d132
4 touches
1 conflict
0x196c0976…dde4
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 0x71fad9ce4b…8ac11f
Audit this contract →
← previous block·next block →recent activity