← previous blocknext block →recent activity
Analyzing
Block #99,308,868
36 transactions · 30 stateful · 2026-08-26 10:47:21 UTC
Parallelism
61/100
Blocked
67%
Avg conflicts / tx
2.03
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #99,308,868 · 36 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w07w112w013w114w215w316w017w118w119w220w323w525w626w729w430w832w1034w1235w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xd814f518…f5b4
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0x0ec34d4f…5fa1
0x34b655…2a6f
8 touches
6 conflicts
0x4c574adc…611d
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity