← previous blocknext block →recent activity

Analyzing

Block #108,498,252

21 transactions · 21 stateful · 2026-09-27 15:14:30 UTC

Parallelism

67/100

Blocked

48%

Avg conflicts / tx

1.1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #108,498,252  ·  21 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

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0xaad6be10…0801

0x2a68ba…90c5

10 touches
10 conflicts

0xb7b446d2…2006

0x34b655…2a6f

8 touches
6 conflicts

0xb87af72a…aef6

0x2a68ba…90c5

6 touches
3 conflicts

0x06e40499…165e

0x34ae4d…3fc5

6 touches
3 conflicts

0xa17ec269…7cdd

0x34ae4d…3fc5

6 touches
3 conflicts

0xa605468c…1bfc

0x34ae4d…3fc5

6 touches
3 conflicts

0xc8525006…2b45

0x34ae4d…3fc5

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 0xea02471df2…601542

← previous block·next block →recent activity