← previous blocknext block →recent activity
Analyzing
Block #95,022,292
23 transactions · 20 stateful · 2026-08-11 09:11:07 UTC
Parallelism
70/100
Blocked
60%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,022,292 · 23 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
1w02w03w14w15w28w29w311w412w513w614w015w116w217w522w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
8 touches
6 conflicts
0x2b54cadb…4425
0xd18b7e…414b
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x4acbdbcf…a8c6
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
15 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity