← previous blocknext block →recent activity
Analyzing
Block #106,207,103
21 transactions · 19 stateful · 2026-09-19 14:59:22 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,207,103 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w07w18w19w010w111w215w016w117w218w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a9b0c45…237c
0x6f6493…b480
8 touches
6 conflicts
0x1e82ef99…59a1
0x6f6493…b480
8 touches
6 conflicts
0x26b57790…9120
0x6f6493…b480
8 touches
6 conflicts
0x2bc2b70d…154f
0x6f6493…b480
8 touches
6 conflicts
0x2dd95dfe…83d1
0x6f6493…b480
8 touches
6 conflicts
0x334740a3…a821
0x6f6493…b480
8 touches
6 conflicts
0x46825c76…6ee2
0x6f6493…b480
8 touches
6 conflicts
0x48672ea3…927a
0x6f6493…b480
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: 0x6f6493e3…08b480
6 conflicts on slot 0x0a9b0c458d…1b237c
Audit this contract →
← previous block·next block →recent activity