← previous blocknext block →recent activity
Analyzing
Block #99,953,033
29 transactions · 24 stateful · 2026-08-28 17:03:48 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,953,033 · 29 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
1w04w05w08w112w113w115w016w117w219w020w121w222w326w127w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c812b49…5329
0x34b655…2a6f
6 touches
3 conflicts
0xc7954a60…d294
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xe73a5eb9…5d49
0x34b655…2a6f
6 touches
3 conflicts
0x10a5a231…be40
0x34b655…2a6f
6 touches
3 conflicts
0xb482658a…e4f5
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd97b0449…00a0
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
3 conflicts on slot 0x1c812b4989…dc5329
Audit this contract →
← previous block·next block →recent activity