← previous blocknext block →recent activity
Analyzing
Block #98,756,432
26 transactions · 26 stateful · 2026-08-24 12:21:02 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,756,432 · 26 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
2w03w14w25w27w08w221w122w323w424w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x3f81bcfb…2905
0x40c49f…2af0
6 touches
3 conflicts
0x9816fc81…4f3c
0x34b655…2a6f
4 touches
1 conflict
0x9cf9008a…d826
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity