← previous blocknext block →recent activity
Analyzing
Block #105,760,882
60 transactions · 52 stateful · 2026-09-18 01:31:06 UTC
Parallelism
72/100
Blocked
69%
Avg conflicts / tx
3.27
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #105,760,882 · 60 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
1w02w13w24w35w46w57w614w733w134w235w336w437w538w639w740w841w942w1043w1144w1245w1346w1447w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88e92ec7…696d
0x34b655…2a6f
30 touches
105 conflicts
0xa7ab3866…c0c7
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x49890ced…6f23
0x34b655…2a6f
16 touches
28 conflicts
0xcf5c81bd…a37f
0xd32edf…ff58
15 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0xfac61869…a561
0x1b6862…e19c
14 touches
21 conflicts
0x07a8122e…a472
0x34b655…2a6f
14 touches
21 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
105 conflicts on slot 0x88e92ec750…6f696d
Audit this contract →
← previous block·next block →recent activity