← previous blocknext block →recent activity

Analyzing

Block #108,300,093

17 transactions · 17 stateful · 2026-09-26 22:37:11 UTC

Parallelism

88/100

Blocked

29%

Avg conflicts / tx

0.35

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #108,300,093  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x045532dd…4b7d

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x14e55cb5…e18f

0xd32edf…ff58

3 touches
1 conflict

0x00000000…0002

0x125f12…a50b

2 touches
0 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

1 conflict on slot 0x045532dd4b…244b7d

← previous block·next block →recent activity