← previous blocknext block →recent activity
Analyzing
Block #99,308,350
31 transactions · 27 stateful · 2026-08-26 10:44:45 UTC
Parallelism
77/100
Blocked
56%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,308,350 · 31 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
1w02w14w05w17w18w09w010w112w118w219w320w221w322w325w426w528w530w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd814f518…f5b4
0x34b655…2a6f
8 touches
6 conflicts
0x810a3aa2…0227
0x34b655…2a6f
8 touches
6 conflicts
0x8ce4d0fa…3a00
0xd32edf…ff58
7 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x300807d1…7aa5
0x34b655…2a6f
6 touches
3 conflicts
0x613a959a…b9cf
0x34b655…2a6f
6 touches
3 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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity