← previous blocknext block →recent activity
Analyzing
Block #98,926,309
13 transactions · 13 stateful · 2026-08-25 02:35:52 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,926,309 · 13 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
2w03w14w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x251861eb…78fd
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x81e6bc22…92bc
0x065c9d…c394
2 touches
0 conflicts
0x99d7899f…d79e
0x065c9d…c394
2 touches
0 conflicts
0xbb60b790…326d
0x065c9d…c394
2 touches
0 conflicts
0xff431830…b83c
0x065c9d…c394
2 touches
0 conflicts
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 0x251861ebbf…b678fd
Audit this contract →
← previous block·next block →recent activity