← previous blocknext block →recent activity
Analyzing
Block #106,041,035
36 transactions · 27 stateful · 2026-09-19 01:03:35 UTC
Parallelism
78/100
Blocked
52%
Avg conflicts / tx
1.06
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,041,035 · 36 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
1w06w17w212w013w114w015w116w217w018w119w220w321w422w528w331w632w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65903ef9…2567
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xe3e67fe3…e754
0x37db7f…ec7b
10 touches
10 conflicts
0x5164ab0e…01e1
0xc8689a…ee79
10 touches
10 conflicts
0x3f152ba8…cea6
0x34b655…2a6f
10 touches
10 conflicts
0x45885570…ed97
0x34b655…2a6f
10 touches
10 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
10 touches
10 conflicts
0x68292fe7…d918
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
21 conflicts on slot 0x65903ef9a0…7d2567
Audit this contract →
← previous block·next block →recent activity