← previous blocknext block →recent activity

Analyzing

Block #105,608,470

25 transactions · 23 stateful · 2026-09-17 12:43:58 UTC

Parallelism

48/100

Blocked

57%

Avg conflicts / tx

1.76

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #105,608,470  ·  25 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6426

0x34b655…2a6f

8 touches
6 conflicts

0x8f84702c…c5f9

0x34b655…2a6f

8 touches
6 conflicts

0xfdc57502…d80e

0x34b655…2a6f

6 touches
3 conflicts

0x4f3d1bb8…76b3

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

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 0xca841faae5…71486a

← previous block·next block →recent activity