← previous blocknext block →recent activity
Analyzing
Block #106,272,637
23 transactions · 21 stateful · 2026-09-19 20:29:14 UTC
Parallelism
65/100
Blocked
57%
Avg conflicts / tx
1.22
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,272,637 · 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
1w02w13w24w05w17w39w212w213w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7bb4e098…a360
0x34b655…2a6f
10 touches
10 conflicts
0xba65d335…5a78
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
8 touches
6 conflicts
0x45b67460…28a5
0x1b6862…e19c
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
10 conflicts on slot 0x7bb4e098a9…09a360
Audit this contract →
← previous block·next block →recent activity