← previous blocknext block →recent activity
Analyzing
Block #99,113,768
7 transactions · 5 stateful · 2026-08-25 18:25:38 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,113,768 · 7 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x109d8a52…a7b7
0x34b655…2a6f
4 touches
1 conflict
0x46e2bb67…d8b3
0x34b655…2a6f
4 touches
1 conflict
0x4be85525…30dc
0x34b655…2a6f
4 touches
1 conflict
0x00922007…8084
0x34b655…2a6f
2 touches
0 conflicts
0x00f6a8a7…0e6e
0x34b655…2a6f
2 touches
0 conflicts
0x5451de01…be8e
0x34b655…2a6f
2 touches
0 conflicts
0x638fa9e2…f0b3
0x34b655…2a6f
2 touches
0 conflicts
0x91508d45…318b
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 0x109d8a5293…02a7b7
Audit this contract →
← previous block·next block →recent activity