← previous blocknext block →recent activity

Analyzing

Block #107,786,130

22 transactions · 17 stateful · 2026-09-25 03:30:16 UTC

Parallelism

77/100

Blocked

41%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #107,786,130  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x11b69a7e…334e

0x01bff4…1071

10 touches
10 conflicts

0x07b86c51…cdae

0x2a68ba…90c5

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0xc95c8716…842d

0x851145…3f07

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x65903ef9…2567

0x34b655…2a6f

4 touches
1 conflict

0x72fb6f45…ed1a

0x34b655…2a6f

4 touches
1 conflict

0x81a97585…bbd1

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: 0x01bff417…bc1071

10 conflicts on slot 0x11b69a7ea1…83334e

← previous block·next block →recent activity