← previous blocknext block →recent activity
Analyzing
Block #99,210,669
18 transactions · 17 stateful · 2026-08-26 02:33:15 UTC
Parallelism
61/100
Blocked
41%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,210,669 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w28w311w412w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d03bddb…6658
0x34b655…2a6f
14 touches
21 conflicts
0x9bf019ed…6b13
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5c1b956d…14d3
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
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
21 conflicts on slot 0x0d03bddb26…a56658
Audit this contract →
← previous block·next block →recent activity