← previous blocknext block →recent activity
Analyzing
Block #98,723,286
20 transactions · 18 stateful · 2026-08-24 09:34:09 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,723,286 · 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
2w03w14w29w010w111w012w113w214w315w418w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0ec919e…4dee
0x40c49f…2af0
10 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe3d7c1f1…1f50
0x34b655…2a6f
4 touches
1 conflict
0xb5cddf91…0abf
0x34b655…2a6f
4 touches
1 conflict
0xc3baa205…f26e
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: 0x40c49f17…d22af0
10 conflicts on slot 0xc0ec919ec2…ba4dee
Audit this contract →
← previous block·next block →recent activity