← previous blocknext block →recent activity

Analyzing

Block #107,812,856

23 transactions · 22 stateful · 2026-09-25 05:44:56 UTC

Parallelism

70/100

Blocked

36%

Avg conflicts / tx

0.83

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #107,812,856  ·  23 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

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0x49890ced…6f23

0x34b655…2a6f

8 touches
6 conflicts

0x60a536a6…ef7a

0x34b655…2a6f

6 touches
3 conflicts

0xdc713589…4901

0x34b655…2a6f

6 touches
3 conflicts

0xa23b9051…392f

0x34b655…2a6f

6 touches
3 conflicts

0x740fff9f…4244

0x34b655…2a6f

6 touches
3 conflicts

0x2b76a1fb…fdfc

0x34b655…2a6f

6 touches
3 conflicts

0x302767c5…403f

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

6 conflicts on slot 0x42522e76ce…082592

← previous block·next block →recent activity