← previous blocknext block →recent activity

Analyzing

Block #104,204,890

20 transactions · 20 stateful · 2026-09-12 14:36:20 UTC

Parallelism

65/100

Blocked

40%

Avg conflicts / tx

1.1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #104,204,890  ·  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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0xac9e0b10…4f67

0x34b655…2a6f

10 touches
10 conflicts

0xa71f18e1…6bb6

0x34b655…2a6f

8 touches
6 conflicts

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0xd7908b5f…56b9

0x34b655…2a6f

6 touches
3 conflicts

0x4147b177…c9ba

0x34b655…2a6f

6 touches
3 conflicts

0x6636a104…d595

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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity