← previous blocknext block →recent activity

Analyzing

Block #107,812,832

29 transactions · 24 stateful · 2026-09-25 05:44:48 UTC

Parallelism

76/100

Blocked

42%

Avg conflicts / tx

0.97

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #107,812,832  ·  29 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

0x2b76a1fb…fdfc

0x34b655…2a6f

14 touches
21 conflicts

0x60a536a6…ef7a

0x34b655…2a6f

10 touches
10 conflicts

0x09cde294…0145

0x34b655…2a6f

10 touches
10 conflicts

0xfcb62b02…d76b

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…002f

0x1b6862…e19c

6 touches
3 conflicts

0xd5b10148…e638

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x152f8e3d…3da0

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 0x2b76a1fb53…5afdfc

← previous block·next block →recent activity