← previous blocknext block →recent activity
Analyzing
Block #99,355,877
24 transactions · 23 stateful · 2026-08-26 14:43:54 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,355,877 · 24 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
1w02w04w15w06w17w18w29w313w418w119w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec162e6c…be77
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb3aa2022…9e09
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xe283e878…7262
0x34b655…2a6f
6 touches
3 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
4 touches
1 conflict
0xc3baa205…f26e
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
3 conflicts on slot 0xec162e6c9a…a9be77
Audit this contract →
← previous block·next block →recent activity