← previous blocknext block →recent activity
Analyzing
Block #99,606,175
18 transactions · 18 stateful · 2026-08-27 11:49:10 UTC
Parallelism
56/100
Blocked
44%
Avg conflicts / tx
1.28
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,606,175 · 18 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w19w211w312w413w514w616w117w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51af0e92…4020
0x34b655…2a6f
10 touches
10 conflicts
0x014e90b3…470f
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xba6ef0ed…bd43
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x51af0e92a5…be4020
Audit this contract →
← previous block·next block →recent activity