← previous blocknext block →recent activity
Analyzing
Block #106,424,861
13 transactions · 12 stateful · 2026-09-20 09:15:17 UTC
Parallelism
39/100
Blocked
58%
Avg conflicts / tx
1.38
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,424,861 · 13 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
2w03w14w25w36w47w511w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
10 touches
10 conflicts
0x3b65c5ca…9f83
0x34b655…2a6f
10 touches
10 conflicts
0x4a45b318…9716
0x34b655…2a6f
10 touches
10 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
10 touches
10 conflicts
0x5f76b8ee…ecfe
0x34b655…2a6f
10 touches
10 conflicts
0x74cdc294…26a8
0x34b655…2a6f
10 touches
10 conflicts
0x88fc2a68…3918
0x34b655…2a6f
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity