← previous blocknext block →recent activity
Analyzing
Block #106,282,226
26 transactions · 26 stateful · 2026-09-19 21:17:29 UTC
Parallelism
77/100
Blocked
62%
Avg conflicts / tx
1.12
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,282,226 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w17w28w29w310w111w214w416w217w321w323w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf64e5e6…75e8
0x34b655…2a6f
8 touches
6 conflicts
0xfac38cc8…fb9d
0x34b655…2a6f
8 touches
6 conflicts
0x997aea7d…1b09
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x07b5c6c6…8863
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
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: Perpl
6 conflicts on slot 0xdf64e5e6b0…c975e8
Audit this contract →
← previous block·next block →recent activity