← previous blocknext block →recent activity

Analyzing

Block #104,159,541

16 transactions · 15 stateful · 2026-09-12 10:46:12 UTC

Parallelism

56/100

Blocked

60%

Avg conflicts / tx

1.94

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #104,159,541  ·  16 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

0xe78db488…80f8

0x34b655…2a6f

14 touches
21 conflicts

0x1408e7c7…f324

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc87e767e…4bba

0x34b655…2a6f

6 touches
3 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

0x3111a64f…eb7f

0x34b655…2a6f

4 touches
1 conflict

0x4ccfe55c…de03

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

21 conflicts on slot 0xe78db48806…4e80f8

← previous block·next block →recent activity