← previous blocknext block →recent activity
Analyzing
Block #99,121,317
20 transactions · 18 stateful · 2026-08-25 19:03:44 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,121,317 · 20 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
1w02w09w010w112w113w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c507f1b…3bf5
0x34b655…2a6f
6 touches
3 conflicts
0xf3bb8b23…c6f0
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x48b13e5e…3c2a
0x34b655…2a6f
4 touches
1 conflict
0x676207a8…5d7e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x947bb79d…6458
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 0x1c507f1bb2…7b3bf5
Audit this contract →
← previous block·next block →recent activity