← previous blocknext block →recent activity
Analyzing
Block #106,388,773
25 transactions · 23 stateful · 2026-09-20 06:13:41 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,388,773 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w112w013w115w016w117w119w020w121w222w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c2761c0…476e
0x34b655…2a6f
6 touches
3 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
6 touches
3 conflicts
0xfece6852…70f3
0x34b655…2a6f
6 touches
3 conflicts
0x038b9243…553d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x524f0872…0d12
0x34b655…2a6f
4 touches
1 conflict
0xd52cdd17…928b
0x99c7a7…8bf0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
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
3 conflicts on slot 0x2c2761c0a9…ff476e
Audit this contract →
← previous block·next block →recent activity