← previous blocknext block →recent activity
Analyzing
Block #106,235,712
53 transactions · 46 stateful · 2026-09-19 17:23:25 UTC
Parallelism
55/100
Blocked
78%
Avg conflicts / tx
3.81
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #106,235,712 · 53 txs across 24 waves · depth 24
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
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w819w721w928w1544w1849w20
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9470055…bbf8
0x34b655…2a6f
22 touches
55 conflicts
0x482471ad…122f
0x34b655…2a6f
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0x38fec752…1345
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…002f
0x1b6862…e19c
14 touches
21 conflicts
0x84611dd3…b348
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
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
55 conflicts on slot 0xf94700553e…5dbbf8
Audit this contract →
← previous block·next block →recent activity