← previous blocknext block →recent activity

Analyzing

Block #104,192,853

24 transactions · 22 stateful · 2026-09-12 13:35:03 UTC

Parallelism

63/100

Blocked

50%

Avg conflicts / tx

1.17

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #104,192,853  ·  24 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

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0xb8632b42…d1a3

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x20282983…15f3

0x34b655…2a6f

6 touches
3 conflicts

0x7ef4ba09…2a25

0x34b655…2a6f

6 touches
3 conflicts

0x5d6da397…6c5c

0x34b655…2a6f

6 touches
3 conflicts

0xb9b077a8…e029

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 0xc824469a90…af6425

← previous block·next block →recent activity