← previous blocknext block →recent activity
Analyzing
Block #99,196,863
26 transactions · 21 stateful · 2026-08-26 01:23:48 UTC
Parallelism
77/100
Blocked
62%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,196,863 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w37w18w110w011w113w214w316w217w418w324w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd36ed1d5…b4df
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x41c56387…a8f6
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x258fcaf5…2084
0x34b655…2a6f
4 touches
1 conflict
0x55010ec8…ea31
0x34b655…2a6f
4 touches
1 conflict
0xb1856468…e84f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0xd36ed1d56a…e0b4df
Audit this contract →
← previous block·next block →recent activity