← previous blocknext block →recent activity
Analyzing
Block #105,850,307
19 transactions · 19 stateful · 2026-09-18 09:02:36 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,850,307 · 19 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
3w06w17w28w310w011w113w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08cc68a2…2a59
0x34b655…2a6f
10 touches
10 conflicts
0x0e9337e1…9956
0x34b655…2a6f
10 touches
10 conflicts
0xee8237bd…46ad
0x34b655…2a6f
8 touches
6 conflicts
0x30eb4826…3990
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
6 touches
3 conflicts
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0xf28ea1d1…1fb8
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
10 conflicts on slot 0x08cc68a2c8…482a59
Audit this contract →
← previous block·next block →recent activity