← previous blocknext block →recent activity
Analyzing
Block #98,749,643
24 transactions · 21 stateful · 2026-08-24 11:46:44 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,749,643 · 24 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
2w03w04w15w16w111w012w014w115w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79c9c57c…8c3e
0x34b655…2a6f
4 touches
1 conflict
0xac389ba9…8b45
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xc551df49…4b23
0x40c49f…2af0
4 touches
1 conflict
0x9a3068dd…18f1
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
1 conflict on slot 0x79c9c57c6e…d38c3e
Audit this contract →
← previous block·next block →recent activity