← previous blocknext block →recent activity

Analyzing

Block #106,155,704

20 transactions · 19 stateful · 2026-09-19 10:40:40 UTC

Parallelism

65/100

Blocked

47%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #106,155,704  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xc68dcec0…21c8

0x34b655…2a6f

12 touches
15 conflicts

0xaa3b4402…74e6

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xd17580f9…ece1

0x754704…b603

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xfcc8f826…7c5f

0x34b655…2a6f

6 touches
3 conflicts

0x4d4389b2…6e07

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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

15 conflicts on slot 0xc68dcec0c2…4e21c8

← previous block·next block →recent activity