← previous blocknext block →recent activity
Analyzing
Block #99,487,106
33 transactions · 30 stateful · 2026-08-27 01:44:50 UTC
Parallelism
76/100
Blocked
57%
Avg conflicts / tx
1.39
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,487,106 · 33 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w09w110w011w112w213w114w315w320w021w122w223w327w428w530w531w632w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd814f518…f5b4
0x34b655…2a6f
10 touches
10 conflicts
0x8ffa3328…ce11
0xe52b14…7230
10 touches
10 conflicts
0xf275b4ca…57b8
0xe52b14…7230
8 touches
6 conflicts
0xb75d08b2…3e12
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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: 0xe52b1424…bb7230
15 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity