← previous blocknext block →recent activity
Analyzing
Block #106,198,332
25 transactions · 24 stateful · 2026-09-19 14:15:11 UTC
Parallelism
76/100
Blocked
54%
Avg conflicts / tx
1.28
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,198,332 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w08w110w112w214w315w016w117w418w519w020w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4f2f9cd…acee
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c5
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x6a9e408e…3721
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 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 0xd4f2f9cdbe…56acee
Audit this contract →
← previous block·next block →recent activity