← previous blocknext block →recent activity
Analyzing
Block #106,428,015
23 transactions · 21 stateful · 2026-09-20 09:31:09 UTC
Parallelism
65/100
Blocked
52%
Avg conflicts / tx
1.3
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,428,015 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w17w213w314w418w519w620w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x74e46435…fdcd
0x34b655…2a6f
8 touches
6 conflicts
0x0001a9e9…9bcd
0x34b655…2a6f
8 touches
6 conflicts
0x9ea1ca97…7b41
0x34b655…2a6f
8 touches
6 conflicts
0xc78b8610…8ca1
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
8 touches
6 conflicts
0xecd87a39…d9c5
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
6 conflicts on slot 0x49b9fdd5ff…6f9c16
Audit this contract →
← previous block·next block →recent activity