← previous blocknext block →recent activity

Analyzing

Block #108,664,069

23 transactions · 19 stateful · 2026-09-28 05:09:31 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

0.52

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #108,664,069  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

6 touches
3 conflicts

0xb991f1e1…5e32

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xfae0ef61…5a9b

0x065c9d…c394

4 touches
1 conflict

0xb87af72a…aef6

0x2a68ba…90c5

4 touches
1 conflict

0x06e40499…165e

0x34ae4d…3fc5

4 touches
1 conflict

0x1b60b708…5b4b

0x34ae4d…3fc5

4 touches
1 conflict

0x02ee3e98…d4fc

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

3 conflicts on slot 0x42522e76ce…082592

← previous block·next block →recent activity