← previous blocknext block →recent activity
Analyzing
Block #99,170,996
13 transactions · 12 stateful · 2026-08-25 23:13:39 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,170,996 · 13 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
2w06w07w18w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe641a5f2…5d6f
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x1634c5ef…777a
0x34b655…2a6f
2 touches
0 conflicts
0x22ede494…3d3b
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 0xe641a5f2cb…2b5d6f
Audit this contract →
← previous block·next block →recent activity