← previous blocknext block →recent activity
Analyzing
Block #105,852,746
31 transactions · 31 stateful · 2026-09-18 09:14:53 UTC
Parallelism
81/100
Blocked
26%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,852,746 · 31 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
1w03w012w013w014w117w018w120w121w222w323w424w530w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55192654…91fe
0x34b655…2a6f
10 touches
10 conflicts
0xbedc081c…929b
0x34b655…2a6f
10 touches
10 conflicts
0xab981df1…2941
0x34b655…2a6f
8 touches
6 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
6 touches
3 conflicts
0x206f4379…e08a
0x34b655…2a6f
6 touches
3 conflicts
0x00216970…a965
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
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
10 conflicts on slot 0x551926541c…2e91fe
Audit this contract →
← previous block·next block →recent activity