← previous blocknext block →recent activity
Analyzing
Block #99,317,650
10 transactions · 10 stateful · 2026-08-26 11:31:32 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,317,650 · 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
2w03w14w06w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ce25dbc…9059
0x34b655…2a6f
4 touches
1 conflict
0x7e4547a3…c7d0
0x34b655…2a6f
4 touches
1 conflict
0xc62744fa…d289
0x34b655…2a6f
4 touches
1 conflict
0xd2dfd9bc…3eec
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x39bef825…5bee
0x34b655…2a6f
4 touches
1 conflict
0x1f5a2e2b…65f1
0x2b46c0…1669
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
1 conflict on slot 0x6ce25dbc63…7a9059
Audit this contract →
← previous block·next block →recent activity