← previous blocknext block →recent activity
Analyzing
Block #106,017,318
22 transactions · 19 stateful · 2026-09-18 23:04:13 UTC
Parallelism
73/100
Blocked
58%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,017,318 · 22 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
1w02w13w24w06w07w18w19w210w312w013w114w216w419w020w121w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51799411…9ca7
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x39561c15…c70f
0x34b655…2a6f
6 touches
3 conflicts
0xeddd84a1…6105
0x73ca90…1130
6 touches
3 conflicts
0xeddd84a1…6106
0x73ca90…1130
6 touches
3 conflicts
0x091c98db…c487
0x6f6493…b480
5 touches
3 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: Perpl
6 conflicts on slot 0x5179941176…4d9ca7
Audit this contract →
← previous block·next block →recent activity