← previous blocknext block →recent activity

Analyzing

Block #108,503,620

23 transactions · 21 stateful · 2026-09-27 15:41:32 UTC

Parallelism

70/100

Blocked

43%

Avg conflicts / tx

0.91

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #108,503,620  ·  23 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xd739490d…821e

0x34b655…2a6f

6 touches
3 conflicts

0x7bd229ad…63b2

0x34b655…2a6f

6 touches
3 conflicts

0xf5dc501b…831c

0x34b655…2a6f

6 touches
3 conflicts

0x47405fe8…b765

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

4 touches
1 conflict

0x532af68d…503d

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity