← previous blocknext block →recent activity
Analyzing
Block #99,082,979
16 transactions · 15 stateful · 2026-08-25 15:50:36 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,082,979 · 16 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
6w09w010w011w112w113w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2506346c…7887
0x8964d7…10f8
4 touches
1 conflict
0x2506346c…7888
0x8964d7…10f8
4 touches
1 conflict
0x2506346c…788b
0x8964d7…10f8
4 touches
1 conflict
0x2506346c…788c
0x8964d7…10f8
4 touches
1 conflict
0x2506346c…788e
0x8964d7…10f8
4 touches
1 conflict
0x39773cec…38ed
0xa6afd3…d132
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x9c6a9da2…c628
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: 0x8964d7c9…5b10f8
1 conflict on slot 0x2506346c7e…397887
Audit this contract →
← previous block·next block →recent activity