← previous blocknext block →recent activity
Analyzing
Block #105,583,891
16 transactions · 16 stateful · 2026-09-17 10:40:14 UTC
Parallelism
69/100
Blocked
44%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,583,891 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w08w19w210w311w412w013w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x189b37d9…f16e
0x6f6493…b480
10 touches
10 conflicts
0x32913bbf…030b
0x6f6493…b480
10 touches
10 conflicts
0x4b043203…6e1f
0x6f6493…b480
10 touches
10 conflicts
0x7a3d9290…7978
0x6f6493…b480
10 touches
10 conflicts
0x8ae92eeb…0853
0x6f6493…b480
10 touches
10 conflicts
0x8ae92eeb…0857
0x6f6493…b480
10 touches
10 conflicts
0xa2210a5e…9ebc
0x6f6493…b480
10 touches
10 conflicts
0xf3ec7902…3770
0x6f6493…b480
10 touches
10 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
10 conflicts on slot 0x189b37d97b…f2f16e
Audit this contract →
← previous block·next block →recent activity