← previous blocknext block →recent activity
Analyzing
Block #106,915,812
22 transactions · 22 stateful · 2026-09-22 02:27:19 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
1.68
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,915,812 · 22 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
1w02w14w06w07w18w29w310w411w212w313w414w515w616w717w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9375a764…dca1
0x34b655…2a6f
14 touches
21 conflicts
0x3a49bf4a…7dee
0x34b655…2a6f
12 touches
15 conflicts
0x85bfd0af…ce96
0x34b655…2a6f
12 touches
15 conflicts
0xccebf5c5…8758
0x34b655…2a6f
12 touches
15 conflicts
0x08e2f7cd…82ab
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x59658b83…222a
0x1b6862…e19c
4 touches
1 conflict
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 0x9375a764b5…f0dca1
Audit this contract →
← previous block·next block →recent activity