← previous blocknext block →recent activity
Analyzing
Block #105,749,062
20 transactions · 20 stateful · 2026-09-18 00:31:38 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,749,062 · 20 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
1w02w111w012w113w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046c8941…e261
0x6f6493…b480
12 touches
15 conflicts
0x1b188575…0129
0x6f6493…b480
12 touches
15 conflicts
0x1c716f7a…5629
0x6f6493…b480
12 touches
15 conflicts
0x2505163a…d015
0x6f6493…b480
12 touches
15 conflicts
0x2670e2f0…fccb
0x6f6493…b480
12 touches
15 conflicts
0x2a8fc2fc…009f
0x6f6493…b480
12 touches
15 conflicts
0x31f18b4a…ecac
0x6f6493…b480
12 touches
15 conflicts
0x342132e2…49b8
0x6f6493…b480
12 touches
15 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: 0x6f6493e3…08b480
15 conflicts on slot 0x046c894163…4ee261
Audit this contract →
← previous block·next block →recent activity