← previous blocknext block →recent activity
Analyzing
Block #106,916,486
33 transactions · 32 stateful · 2026-09-22 02:30:43 UTC
Parallelism
61/100
Blocked
59%
Avg conflicts / tx
1.85
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,916,486 · 33 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w09w111w012w113w014w115w216w317w418w520w621w722w823w924w1025w1126w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46483cb1…e7ca
0x34b655…2a6f
16 touches
28 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
14 touches
21 conflicts
0xccebf5c5…8758
0x34b655…2a6f
14 touches
21 conflicts
0x9a339ea4…3cd6
0x34b655…2a6f
14 touches
21 conflicts
0x3b948d19…8c39
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
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
28 conflicts on slot 0x46483cb14f…c1e7ca
Audit this contract →
← previous block·next block →recent activity