← previous blocknext block →recent activity
Analyzing
Block #106,921,861
41 transactions · 39 stateful · 2026-09-22 02:57:46 UTC
Parallelism
59/100
Blocked
69%
Avg conflicts / tx
2.83
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,921,861 · 41 txs across 17 waves · depth 17
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
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w19w010w111w212w313w414w515w616w717w818w921w1034w1336w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x469dac8d…3411
0x34b655…2a6f
22 touches
55 conflicts
0x34eb3605…9253
0x34b655…2a6f
20 touches
45 conflicts
0x49890ced…6f23
0x34b655…2a6f
20 touches
45 conflicts
0x7ca519d1…4f93
0x34b655…2a6f
18 touches
36 conflicts
0x8590b692…b267
0x34b655…2a6f
18 touches
36 conflicts
0xccebf5c5…8758
0x34b655…2a6f
18 touches
36 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x83e5f293…4db6
0x34b655…2a6f
8 touches
6 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
55 conflicts on slot 0x469dac8dcd…223411
Audit this contract →
← previous block·next block →recent activity