← previous blocknext block →recent activity
Analyzing
Block #94,962,993
10 transactions · 10 stateful · 2026-08-11 04:12:51 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,962,993 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae5cb3e3…b10f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xd359eaf2…7fea
0x065c9d…c394
4 touches
1 conflict
0x22e0cc1d…ad15
0x34b655…2a6f
2 touches
0 conflicts
0x28d9aaeb…ef07
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xae5cb3e39b…73b10f
Audit this contract →
← previous block·next block →recent activity