← previous blocknext block →recent activity
Analyzing
Block #99,193,722
12 transactions · 12 stateful · 2026-08-26 01:08:00 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,193,722 · 12 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
5w08w19w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b65f692…2bb2
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x6a673ab4…355a
0x34b655…2a6f
4 touches
1 conflict
0x6ef279f3…4f7e
0x34b655…2a6f
4 touches
1 conflict
0x2202504e…fad0
0x34b655…2a6f
2 touches
0 conflicts
0xb688ed23…1cf3
0x34b655…2a6f
2 touches
0 conflicts
0xb6ed511f…6b68
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 0x9b65f692e1…fe2bb2
Audit this contract →
← previous block·next block →recent activity