← previous blocknext block →recent activity
Analyzing
Block #106,934,058
21 transactions · 20 stateful · 2026-09-22 03:59:09 UTC
Parallelism
62/100
Blocked
65%
Avg conflicts / tx
1.95
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,934,058 · 21 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
1w02w13w24w36w08w09w110w211w312w413w514w615w718w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7aa9720…56df
0x34b655…2a6f
16 touches
28 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
16 touches
28 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
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
28 conflicts on slot 0xb7aa972000…2456df
Audit this contract →
← previous block·next block →recent activity