← previous blocknext block →recent activity

Analyzing

Block #107,824,427

27 transactions · 20 stateful · 2026-09-25 06:43:10 UTC

Parallelism

74/100

Blocked

40%

Avg conflicts / tx

0.81

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #107,824,427  ·  27 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x42522e76…2592

0x34b655…2a6f

12 touches
15 conflicts

0xe7249229…ad4b

0x34b655…2a6f

8 touches
6 conflicts

0x66fc0764…05fd

0x34b655…2a6f

8 touches
6 conflicts

0x88065e57…c867

0x34b655…2a6f

6 touches
3 conflicts

0xa7ba83b5…d0a8

0x34b655…2a6f

6 touches
3 conflicts

0x60a536a6…ef7a

0x34b655…2a6f

6 touches
3 conflicts

0xcb45d9d6…cb87

0x1b6862…e19c

4 touches
1 conflict

0x00f245ce…1e10

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: Perpl

15 conflicts on slot 0x42522e76ce…082592

← previous block·next block →recent activity