← previous blocknext block →recent activity
Analyzing
Block #106,538,081
27 transactions · 26 stateful · 2026-09-20 18:45:10 UTC
Parallelism
67/100
Blocked
65%
Avg conflicts / tx
2.07
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,538,081 · 27 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w010w111w414w217w318w419w520w621w722w826w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46a5ec6c…f318
0x34b655…2a6f
18 touches
36 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0x6b1259e6…4e12
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x04994ed2…9032
0x34b655…2a6f
10 touches
10 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
36 conflicts on slot 0x46a5ec6cde…19f318
Audit this contract →
← previous block·next block →recent activity