← previous blocknext block →recent activity
Analyzing
Block #106,924,374
37 transactions · 33 stateful · 2026-09-22 03:10:25 UTC
Parallelism
76/100
Blocked
70%
Avg conflicts / tx
1.78
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,924,374 · 37 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w09w610w729w532w835w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x125f12…a50b
16 touches
28 conflicts
0x9abf13e5…fd61
0xd32edf…ff58
11 touches
15 conflicts
0x94dabb65…43a3
0x34b655…2a6f
10 touches
10 conflicts
0x839c0c71…bada
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x77ed432f…fa04
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
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: 0x125f12a1…cda50b
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity