← previous blocknext block →recent activity

Analyzing

Block #108,310,048

27 transactions · 21 stateful · 2026-09-26 23:27:17 UTC

Parallelism

85/100

Blocked

33%

Avg conflicts / tx

0.37

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #108,310,048  ·  27 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x7bd229ad…63b2

0x34b655…2a6f

6 touches
3 conflicts

0xd2d7cba8…9c3a

0x34b655…2a6f

6 touches
3 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0xf5dc501b…831c

0x34b655…2a6f

6 touches
3 conflicts

0xa9a9d0e0…4087

0x34b655…2a6f

4 touches
1 conflict

0xb75367ff…a2b7

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

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

3 conflicts on slot 0x7bd229ade5…6b63b2

← previous block·next block →recent activity