← previous blocknext block →recent activity

Analyzing

Block #107,848,699

20 transactions · 17 stateful · 2026-09-25 08:45:20 UTC

Parallelism

60/100

Blocked

53%

Avg conflicts / tx

1.5

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #107,848,699  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xba522812…1f1f

0x34b655…2a6f

16 touches
28 conflicts

0x8f49a54c…e04c

0x34b655…2a6f

14 touches
21 conflicts

0xf30b9357…2e1e

0x34b655…2a6f

12 touches
15 conflicts

0x23c585cc…1bc7

0x34b655…2a6f

12 touches
15 conflicts

0x62466313…512a

0x34b655…2a6f

10 touches
10 conflicts

0x72083f0d…082a

0x34b655…2a6f

10 touches
10 conflicts

0x42522e76…2592

0x34b655…2a6f

10 touches
10 conflicts

0x49890ced…6f23

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

28 conflicts on slot 0xba52281226…3a1f1f

← previous block·next block →recent activity