← previous blocknext block →recent activity
Analyzing
Block #106,242,752
76 transactions · 61 stateful · 2026-09-19 17:58:51 UTC
Parallelism
75/100
Blocked
82%
Avg conflicts / tx
3.84
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #106,242,752 · 76 txs across 19 waves · depth 19
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
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w617w419w620w723w724w825w927w1033w537w862w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
38 touches
171 conflicts
0xa08ffe9a…c7de
0xd32edf…ff58
19 touches
45 conflicts
0xea02471d…1542
0x34b655…2a6f
16 touches
28 conflicts
0x77ed432f…fa04
0x065c9d…c394
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 conflicts
0x928d6b23…5374
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: 0xf5b5f7f8…a36d70
171 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity