← previous blocknext block →recent activity
Analyzing
Block #106,931,499
40 transactions · 32 stateful · 2026-09-22 03:46:17 UTC
Parallelism
63/100
Blocked
63%
Avg conflicts / tx
3.05
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,931,499 · 40 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w19w210w311w412w513w618w219w320w721w824w728w430w833w934w1035w1136w1237w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
28 touches
91 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
24 touches
66 conflicts
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0xeb1b4ae8…64bd
0x37db7f…ec7b
14 touches
21 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
14 touches
21 conflicts
0x76832384…dc5b
0x34b655…2a6f
14 touches
21 conflicts
0x23c8c8dd…7a42
0x34b655…2a6f
14 touches
21 conflicts
0xa7d3cb90…e1d9
0x34b655…2a6f
14 touches
21 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
91 conflicts on slot 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity