← previous blocknext block →recent activity
Analyzing
Block #99,811,764
8 transactions · 8 stateful · 2026-08-28 05:11:05 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,811,764 · 8 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
2w03w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ba0351f…b71e
0x34b655…2a6f
4 touches
1 conflict
0xd04f5be7…14b5
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0xadc4ee2a…56e4
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x2e6e46d2…a99f
0x34b655…2a6f
2 touches
0 conflicts
0x326a02b5…8dad
0x34b655…2a6f
2 touches
0 conflicts
0x5f4377b4…82eb
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 0x6ba0351f2a…28b71e
Audit this contract →
← previous block·next block →recent activity