← previous blocknext block →recent activity
Analyzing
Block #106,216,697
60 transactions · 48 stateful · 2026-09-19 15:47:40 UTC
Parallelism
73/100
Blocked
71%
Avg conflicts / tx
2.48
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,216,697 · 60 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w29w312w313w421w324w327w428w529w630w731w833w934w1035w1137w1238w1339w1440w1553w554w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
28 touches
91 conflicts
0x839c0c71…bada
0x34b655…2a6f
14 touches
21 conflicts
0x94dabb65…43a3
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x3643741b…109c
0x34b655…2a6f
8 touches
6 conflicts
0x366a19b0…f065
0x34b655…2a6f
8 touches
6 conflicts
0x68292fe7…d918
0x34b655…2a6f
8 touches
6 conflicts
0x81a9b9e0…2b7e
0x34b655…2a6f
8 touches
6 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: 0xf5b5f7f8…a36d70
91 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity