← previous blocknext block →recent activity
Analyzing
Block #106,953,621
25 transactions · 21 stateful · 2026-09-22 05:37:38 UTC
Parallelism
68/100
Blocked
67%
Avg conflicts / tx
1.4
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,953,621 · 25 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
1w02w13w24w35w010w111w212w313w414w515w016w118w323w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bbf13c8…2cee
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
8 touches
6 conflicts
0xf1f81c17…a85a
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xf8480e2a…dff3
0x1b6862…e19c
6 touches
3 conflicts
0x4e58deff…c5d0
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
15 conflicts on slot 0x1bbf13c860…052cee
Audit this contract →
← previous block·next block →recent activity