← previous blocknext block →recent activity
Analyzing
Block #100,784,035
20 transactions · 18 stateful · 2026-08-31 14:49:36 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,784,035 · 20 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
1w02w15w26w08w09w110w112w213w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x382434ca…96b5
0x34b655…2a6f
6 touches
3 conflicts
0x451e482b…7e7d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd2dfd9bc…3eec
0x34b655…2a6f
6 touches
3 conflicts
0x32b2548c…4105
0x34b655…2a6f
6 touches
3 conflicts
0x083a8763…5a7a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x1d9154e7…8821
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
3 conflicts on slot 0x382434ca57…4d96b5
Audit this contract →
← previous block·next block →recent activity