← previous blocknext block →recent activity
Analyzing
Block #99,083,623
18 transactions · 17 stateful · 2026-08-25 15:53:51 UTC
Parallelism
72/100
Blocked
41%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,083,623 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w16w27w311w112w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
6 touches
3 conflicts
0x7efbf74f…f9d2
0x34b655…2a6f
6 touches
3 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
4 touches
1 conflict
0x3b65c5ca…9f83
0x34b655…2a6f
4 touches
1 conflict
0x3c9b10c1…d791
0x34b655…2a6f
4 touches
1 conflict
0x40d6d1e9…131e
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity