← previous blocknext block →recent activity
Analyzing
Block #105,926,274
14 transactions · 14 stateful · 2026-09-18 15:25:50 UTC
Parallelism
79/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,926,274 · 14 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
1w02w13w29w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
6 touches
3 conflicts
0x2a2896a0…2a0a
0x34b655…2a6f
6 touches
3 conflicts
0x742eaa45…c52b
0x34b655…2a6f
6 touches
3 conflicts
0xac1228d4…f289
0x34b655…2a6f
4 touches
1 conflict
0x4073f47e…39e6
0x34b655…2a6f
4 touches
1 conflict
0x0c0ca07f…b78d
0x34b655…2a6f
4 touches
1 conflict
0x5b7854b1…8bab
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity