← previous blocknext block →recent activity
Analyzing
Block #99,209,274
26 transactions · 23 stateful · 2026-08-26 02:26:14 UTC
Parallelism
81/100
Blocked
52%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,209,274 · 26 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
2w03w15w06w07w18w110w114w116w117w218w319w420w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xf81d7343…f97b
0x34b655…2a6f
8 touches
6 conflicts
0x91508d45…318b
0x34b655…2a6f
6 touches
3 conflicts
0x939cdd56…00c8
0x34b655…2a6f
6 touches
3 conflicts
0x46e2bb67…d8b3
0x34b655…2a6f
4 touches
1 conflict
0x7d931aec…78e1
0x34b655…2a6f
4 touches
1 conflict
0xb2d8af24…4750
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity