← previous blocknext block →recent activity
Analyzing
Block #106,473,447
25 transactions · 23 stateful · 2026-09-20 13:19:52 UTC
Parallelism
68/100
Blocked
70%
Avg conflicts / tx
2.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,473,447 · 25 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
1w02w13w24w35w46w07w18w19w212w315w420w221w622w323w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24e6c041…7d6b
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001c
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
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
15 conflicts on slot 0x24e6c04114…167d6b
Audit this contract →
← previous block·next block →recent activity