← previous blocknext block →recent activity

Analyzing

Block #105,881,136

18 transactions · 18 stateful · 2026-09-18 11:37:46 UTC

Parallelism

61/100

Blocked

44%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #105,881,136  ·  18 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

0x9c83a7b1…e305

0x34b655…2a6f

12 touches
15 conflicts

0xb723a202…631d

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xd79c9727…1233

0x34b655…2a6f

6 touches
3 conflicts

0x4abfb389…18f4

0x34b655…2a6f

6 touches
3 conflicts

0x64e1f0ce…7156

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x42522e76…2592

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 0x9c83a7b19e…36e305

← previous block·next block →recent activity