← previous blocknext block →recent activity

Analyzing

Block #107,823,817

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

Parallelism

61/100

Blocked

43%

Avg conflicts / tx

1

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #107,823,817  ·  23 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x22c4a631…90aa

0x34b655…2a6f

12 touches
15 conflicts

0x49890ced…6f23

0x34b655…2a6f

10 touches
10 conflicts

0x31d88d27…7617

0x34b655…2a6f

10 touches
10 conflicts

0xa2c4d203…05b6

0x34b655…2a6f

8 touches
6 conflicts

0xb1360a93…55e8

0x34b655…2a6f

8 touches
6 conflicts

0xc1da8f73…484c

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x28e2f7c3…e848

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

15 conflicts on slot 0x22c4a63119…e590aa

← previous block·next block →recent activity