← previous blocknext block →recent activity
Analyzing
Block #106,198,923
26 transactions · 25 stateful · 2026-09-19 14:18:09 UTC
Parallelism
73/100
Blocked
64%
Avg conflicts / tx
1.42
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,198,923 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w18w211w212w313w415w416w317w418w519w625w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x762445fc…df4d
0x34b655…2a6f
14 touches
21 conflicts
0x05e1eba1…6491
0x34b655…2a6f
10 touches
10 conflicts
0xd911522b…e960
0x34b655…2a6f
8 touches
6 conflicts
0xac0b4a08…faae
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0xd996735f…8734
0x1b6862…e19c
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
21 conflicts on slot 0x762445fc26…37df4d
Audit this contract →
← previous block·next block →recent activity