← previous blocknext block →recent activity
Analyzing
Block #99,155,058
9 transactions · 7 stateful · 2026-08-25 21:53:29 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,155,058 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x3ee8b564…4c49
0x34b655…2a6f
4 touches
1 conflict
0x43f1d2b0…2518
0x34b655…2a6f
4 touches
1 conflict
0x00be305d…7279
0x34b655…2a6f
2 touches
0 conflicts
0x049e16b3…8059
0x34b655…2a6f
2 touches
0 conflicts
0x0c478a49…ed73
0x34b655…2a6f
2 touches
0 conflicts
0x0d816e2e…67a1
0x34b655…2a6f
2 touches
0 conflicts
0x109d8a52…a7b7
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
3 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity