← previous blocknext block →recent activity
Analyzing
Block #106,954,308
57 transactions · 52 stateful · 2026-09-22 05:41:06 UTC
Parallelism
77/100
Blocked
73%
Avg conflicts / tx
2.42
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,954,308 · 57 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
1w02w13w24w35w26w311w112w115w216w317w418w527w428w535w636w737w445w846w947w1048w1149w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0cabc566…f385
0x34b655…2a6f
24 touches
66 conflicts
0xcb21158b…f18d
0x34b655…2a6f
16 touches
28 conflicts
0x67236cfa…8bf7
0x34b655…2a6f
14 touches
21 conflicts
0xa4a1ecf7…9e63
0x34b655…2a6f
14 touches
21 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
14 touches
21 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
12 touches
15 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 0x0cabc56642…c3f385
Audit this contract →
← previous block·next block →recent activity