← previous blocknext block →recent activity
Analyzing
Block #105,843,383
31 transactions · 31 stateful · 2026-09-18 08:27:43 UTC
Parallelism
58/100
Blocked
68%
Avg conflicts / tx
3.45
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #105,843,383 · 31 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
1w02w13w24w15w26w07w210w114w115w216w317w318w419w520w621w722w823w924w1025w1130w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd7f5b55…4994
0x34b655…2a6f
24 touches
66 conflicts
0xc824469a…6425
0x34b655…2a6f
24 touches
66 conflicts
0xa7b1ee0a…cbd8
0x34b655…2a6f
16 touches
28 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x1b49615c…9fbb
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
10 touches
10 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
10 touches
10 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
66 conflicts on slot 0xfd7f5b557f…f74994
Audit this contract →
← previous block·next block →recent activity