← previous blocknext block →recent activity
Analyzing
Block #105,920,797
26 transactions · 22 stateful · 2026-09-18 14:58:15 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,920,797 · 26 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
1w04w05w06w18w010w013w117w118w019w120w221w322w425w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x4089d428…b018
0x34b655…2a6f
8 touches
6 conflicts
0x315e07b8…9823
0x34b655…2a6f
6 touches
3 conflicts
0x34836ffb…2a0b
0x34b655…2a6f
6 touches
3 conflicts
0x2c576cbc…a883
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x3018a378…d7bb
0x34b655…2a6f
4 touches
1 conflict
0xf8f1e808…a4fd
0x34b655…2a6f
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity