← previous blocknext block →recent activity

Analyzing

Block #107,785,561

24 transactions · 16 stateful · 2026-09-25 03:27:25 UTC

Parallelism

79/100

Blocked

50%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #107,785,561  ·  24 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

0x3a663e9a…a9c5

0x508254…98bd

8 touches
6 conflicts

0x3a663e9a…a9cb

0x508254…98bd

8 touches
6 conflicts

0x3a663e9a…a9c8

0x508254…98bd

8 touches
6 conflicts

0x94dabb65…43a3

0x34b655…2a6f

8 touches
6 conflicts

0x3a663e9a…a9c4

0x508254…98bd

8 touches
6 conflicts

0x3a663e9a…a9c7

0x508254…98bd

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xf3d10975…0d07

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: 0x508254c8…4a98bd

6 conflicts on slot 0x3a663e9a3a…2fa9c5

← previous block·next block →recent activity