← previous blocknext block →recent activity
Analyzing
Block #99,859,527
28 transactions · 26 stateful · 2026-08-28 09:12:36 UTC
Parallelism
64/100
Blocked
58%
Avg conflicts / tx
1.43
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,859,527 · 28 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w29w310w411w513w614w716w827w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e805190…dd6b
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x9c9675f7…a878
0x34b655…2a6f
10 touches
10 conflicts
0x014e90b3…470f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x18e86f02…fa98
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x941bd594…21fd
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 0x2e805190bd…24dd6b
Audit this contract →
← previous block·next block →recent activity