← previous blocknext block →recent activity

Analyzing

Block #108,494,999

24 transactions · 23 stateful · 2026-09-27 14:58:07 UTC

Parallelism

63/100

Blocked

48%

Avg conflicts / tx

1.63

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #108,494,999  ·  24 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

0x4c29ecd5…58b6

0x34b655…2a6f

14 touches
21 conflicts

0x9d8078fe…ed70

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x40d6d1e9…131e

0x34b655…2a6f

8 touches
6 conflicts

0x5969523e…5191

0x34b655…2a6f

8 touches
6 conflicts

0x7006165a…df17

0x34b655…2a6f

8 touches
6 conflicts

0x9daafdf9…bb53

0x34b655…2a6f

8 touches
6 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

21 conflicts on slot 0x4c29ecd55a…1058b6

← previous block·next block →recent activity