← previous blocknext block →recent activity

Analyzing

Block #107,816,282

23 transactions · 21 stateful · 2026-09-25 06:02:10 UTC

Parallelism

57/100

Blocked

52%

Avg conflicts / tx

1.22

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #107,816,282  ·  23 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xbdd97c21…e3d0

0x34b655…2a6f

10 touches
10 conflicts

0x49890ced…6f23

0x34b655…2a6f

10 touches
10 conflicts

0xc0893415…913d

0x34b655…2a6f

8 touches
6 conflicts

0x63c421ca…8cde

0x34b655…2a6f

6 touches
3 conflicts

0x72083f0d…082a

0x34b655…2a6f

6 touches
3 conflicts

0x73e7a7d7…a153

0x34b655…2a6f

6 touches
3 conflicts

0xc7679110…572d

0x34b655…2a6f

6 touches
3 conflicts

0x42522e76…2592

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

10 conflicts on slot 0xbdd97c213f…cee3d0

← previous block·next block →recent activity