← previous blocknext block →recent activity
Analyzing
Block #99,958,164
19 transactions · 14 stateful · 2026-08-28 17:29:39 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,958,164 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w011w114w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6d40b7f…2969
0x34b655…2a6f
8 touches
6 conflicts
0x05086df1…bd5a
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0xef048f92…572b
0x34b655…2a6f
4 touches
1 conflict
0xbbdfd584…ab2f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0x49f39582…ccc7
0x754704…b603
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
6 conflicts on slot 0xa6d40b7f0d…ff2969
Audit this contract →
← previous block·next block →recent activity