← previous blocknext block →recent activity
Analyzing
Block #99,249,774
20 transactions · 17 stateful · 2026-08-26 05:50:00 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,249,774 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w313w215w019w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b780b26…f5ff
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0x8cfa9962…2675
0x34b655…2a6f
6 touches
3 conflicts
0x2caeb7f5…b6bb
0x34b655…2a6f
6 touches
3 conflicts
0xb3af6b7b…bba9
0x34b655…2a6f
6 touches
3 conflicts
0x7a3d5e6f…7864
0x34b655…2a6f
4 touches
1 conflict
0x7aa463de…e7b8
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
6 conflicts on slot 0x8b780b2668…85f5ff
Audit this contract →
← previous block·next block →recent activity