← previous blocknext block →recent activity
Analyzing
Block #105,627,051
31 transactions · 29 stateful · 2026-09-17 14:17:31 UTC
Parallelism
68/100
Blocked
45%
Avg conflicts / tx
1.26
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,627,051 · 31 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w08w09w114w016w123w628w730w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8f5e33f…719c
0x34b655…2a6f
14 touches
21 conflicts
0xadd9cc71…4d89
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xab41643c…f9bf
0x34b655…2a6f
8 touches
6 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
8 touches
6 conflicts
0x429c8b35…0f5c
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xa62dce79…e7ff
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
21 conflicts on slot 0xe8f5e33f0f…b6719c
Audit this contract →
← previous block·next block →recent activity