← previous blocknext block →recent activity
Analyzing
Block #105,932,755
32 transactions · 25 stateful · 2026-09-18 15:58:27 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,932,755 · 32 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w118w122w224w225w326w430w531w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x420b5d54…a83e
0x34b655…2a6f
6 touches
3 conflicts
0x3a429191…9cda
0x34b655…2a6f
6 touches
3 conflicts
0x0a9fcba0…98af
0x34b655…2a6f
4 touches
1 conflict
0x3180cd66…aaef
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity