← previous blocknext block →recent activity
Analyzing
Block #99,135,160
10 transactions · 9 stateful · 2026-08-25 20:13:23 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,135,160 · 10 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
2w03w14w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f1801b5…5a4c
0x34b655…2a6f
6 touches
3 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd1b40f29…9b9d
0x34b655…2a6f
4 touches
1 conflict
0x1aa85bda…e324
0x34b655…2a6f
2 touches
0 conflicts
0x2202504e…fad0
0x34b655…2a6f
2 touches
0 conflicts
0x3266bf53…8872
0x34b655…2a6f
2 touches
0 conflicts
0x801a6e57…d85c
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 0x1f1801b522…8c5a4c
Audit this contract →
← previous block·next block →recent activity