← previous blocknext block →recent activity

Analyzing

Block #105,471,111

20 transactions · 18 stateful · 2026-09-17 01:12:39 UTC

Parallelism

85/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #105,471,111  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xee8237bd…46ad

0x34b655…2a6f

4 touches
1 conflict

0xd4f108df…61f6

0x34b655…2a6f

4 touches
1 conflict

0x5e8f1bea…875b

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…1266

0x34b655…2a6f

4 touches
1 conflict

0xb5bf6c79…b71a

0x34b655…2a6f

2 touches
0 conflicts

0xe3d30fe2…d897

0x34b655…2a6f

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

3 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity