← previous blocknext block →recent activity
Analyzing
Block #99,873,825
12 transactions · 9 stateful · 2026-08-28 10:24:37 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,873,825 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x20d08329…c16a
0x34b655…2a6f
4 touches
1 conflict
0x2cc7d2e3…c1af
0x34b655…2a6f
4 touches
1 conflict
0x2999ebda…ce6c
0x34b655…2a6f
2 touches
0 conflicts
0x3344bc7c…fee3
0x34b655…2a6f
2 touches
0 conflicts
0x3bb58c95…b572
0x34b655…2a6f
2 touches
0 conflicts
0x45885570…ed97
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
1 conflict on slot 0x326a02b5c5…5c8dad
Audit this contract →
← previous block·next block →recent activity