← previous blocknext block →recent activity

Analyzing

Block #104,916,652

27 transactions · 26 stateful · 2026-09-15 02:42:02 UTC

Parallelism

67/100

Blocked

46%

Avg conflicts / tx

1.26

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #104,916,652  ·  27 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xa6d40b7f…2969

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0x844b7221…5ad8

0x34b655…2a6f

10 touches
10 conflicts

0x4d4389b2…6e07

0x34b655…2a6f

8 touches
6 conflicts

0xd17580f9…ece1

0x754704…b603

6 touches
3 conflicts

0x5a548af5…0eb0

0x34b655…2a6f

6 touches
3 conflicts

0xd7668c61…55f8

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

21 conflicts on slot 0xa6d40b7f0d…ff2969

← previous block·next block →recent activity