← previous blocknext block →recent activity
Analyzing
Block #99,086,487
15 transactions · 15 stateful · 2026-08-25 16:08:18 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,086,487 · 15 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
2w03w14w07w08w110w011w112w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf660e981…7db7
0x34b655…2a6f
4 touches
2 conflicts
0xec1f21ae…eedc
0x99c7a7…8bf0
4 touches
1 conflict
0xd09a7074…05c9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x37df7523…ccbb
0x754704…b603
4 touches
1 conflict
0xa6eca5ba…4390
0x754704…b603
4 touches
1 conflict
0xf96d61f8…8fd8
0x754704…b603
4 touches
1 conflict
0x3e366689…4d73
0x99c7a7…8bf0
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
2 conflicts on slot 0xf660e9814a…237db7
Audit this contract →
← previous block·next block →recent activity