← previous blocknext block →recent activity
Analyzing
Block #106,466,403
24 transactions · 21 stateful · 2026-09-20 12:44:25 UTC
Parallelism
67/100
Blocked
76%
Avg conflicts / tx
1.88
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,466,403 · 24 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
1w02w13w24w35w16w29w010w111w112w216w317w419w520w622w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac5f3ead…0195
0x34b655…2a6f
14 touches
21 conflicts
0xb1927b58…f161
0x34b655…2a6f
14 touches
21 conflicts
0xe283e878…7262
0x34b655…2a6f
10 touches
10 conflicts
0x63e4750c…d31e
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0x17a7f697…dcb5
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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
21 conflicts on slot 0xac5f3eadc9…b00195
Audit this contract →
← previous block·next block →recent activity