← previous blocknext block →recent activity
Analyzing
Block #106,934,443
21 transactions · 20 stateful · 2026-09-22 04:01:05 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,934,443 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w010w011w112w013w114w215w316w117w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d4ceda4…84c4
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0x8d5fc820…1750
0x34b655…2a6f
8 touches
6 conflicts
0xa0edadb9…dbfe
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf7b76d2f…1b9c
0x34b655…2a6f
6 touches
3 conflicts
0xb50ac9bb…3ff4
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
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 0x3d4ceda45d…bf84c4
Audit this contract →
← previous block·next block →recent activity