← previous blocknext block →recent activity
Analyzing
Block #105,849,900
32 transactions · 30 stateful · 2026-09-18 09:00:34 UTC
Parallelism
59/100
Blocked
67%
Avg conflicts / tx
2.28
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #105,849,900 · 32 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w28w29w217w321w422w523w624w725w826w928w930w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0x23529e13…6f25
0x34b655…2a6f
12 touches
15 conflicts
0xcb778156…7459
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x2827ae77…4368
0x34b655…2a6f
12 touches
15 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00216970…a965
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity