← previous blocknext block →recent activity
Analyzing
Block #105,605,836
40 transactions · 34 stateful · 2026-09-17 12:30:42 UTC
Parallelism
85/100
Blocked
59%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,605,836 · 40 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w07w110w211w012w113w014w115w016w120w021w122w223w329w131w132w233w134w235w236w337w338w439w5
- 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
0xe87ef6db…4042
0xe52b14…7230
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x1f18f001…2c08
0xe52b14…7230
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
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