← previous blocknext block →recent activity
Analyzing
Block #99,091,721
13 transactions · 11 stateful · 2026-08-25 16:34:41 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,091,721 · 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
1w02w110w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x15763bbb…9409
0x34b655…2a6f
2 touches
0 conflicts
0x1f06ee2d…7f6d
0x34b655…2a6f
2 touches
0 conflicts
0x3996c88c…85c0
0x34b655…2a6f
2 touches
0 conflicts
0x6713b018…05f3
0x34b655…2a6f
2 touches
0 conflicts
0x6f644c37…1a87
0x34b655…2a6f
2 touches
0 conflicts
0x9c168b41…7486
0x34b655…2a6f
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity