← previous blocknext block →recent activity
Analyzing
Block #99,859,026
19 transactions · 18 stateful · 2026-08-28 09:10:04 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,859,026 · 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
2w03w14w27w08w19w011w012w114w216w318w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ebc47f3…2d5c
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xbcdd58ff…0711
0x34b655…2a6f
6 touches
3 conflicts
0xac2bc5ca…fb9d
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0xcac3219e…62ce
0x34b655…2a6f
4 touches
1 conflict
0xcc10720d…5f66
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
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 0x2ebc47f341…ea2d5c
Audit this contract →
← previous block·next block →recent activity