← previous blocknext block →recent activity
Analyzing
Block #105,869,744
32 transactions · 29 stateful · 2026-09-18 10:40:26 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
1.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,869,744 · 32 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w08w118w219w320w422w523w624w731w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18a9b62d…d89e
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x23529e13…6f25
0x34b655…2a6f
12 touches
15 conflicts
0xd79c9727…1233
0x34b655…2a6f
10 touches
10 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
10 touches
10 conflicts
0x5fad6fee…7714
0x34b655…2a6f
10 touches
10 conflicts
0x3ca49f3f…b79f
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 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
28 conflicts on slot 0x18a9b62d20…0ad89e
Audit this contract →
← previous block·next block →recent activity