← previous blocknext block →recent activity
Analyzing
Block #106,283,286
33 transactions · 32 stateful · 2026-09-19 21:22:49 UTC
Parallelism
55/100
Blocked
66%
Avg conflicts / tx
2.88
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,283,286 · 33 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w27w08w19w010w111w012w114w315w416w518w519w620w721w822w923w1024w1125w1226w1327w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ee0b65a…6d40
0x34b655…2a6f
24 touches
66 conflicts
0x7849366c…8914
0x34b655…2a6f
22 touches
55 conflicts
0x1b25f260…c429
0x34b655…2a6f
14 touches
21 conflicts
0x652f5f4b…bf8d
0x34b655…2a6f
10 touches
10 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
10 touches
10 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
10 touches
10 conflicts
0x524f0872…0d12
0x34b655…2a6f
10 touches
10 conflicts
0x5d05b007…756a
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 0x4ee0b65a93…c56d40
Audit this contract →
← previous block·next block →recent activity