← previous blocknext block →recent activity

Analyzing

Block #105,932,618

17 transactions · 16 stateful · 2026-09-18 15:57:46 UTC

Parallelism

88/100

Blocked

13%

Avg conflicts / tx

0.12

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #105,932,618  ·  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

0x0d54fa3e…3b3c

0x34b655…2a6f

4 touches
1 conflict

0x12e605da…9ca3

0x34b655…2a6f

4 touches
1 conflict

0x12e77486…ec2b

0x34b655…2a6f

4 touches
1 conflict

0x184e765d…08f6

0x34b655…2a6f

4 touches
1 conflict

0x309f47c0…e1cf

0x34b655…2a6f

4 touches
1 conflict

0x3b65c5ca…9f83

0x34b655…2a6f

4 touches
1 conflict

0x3c9b10c1…d791

0x34b655…2a6f

4 touches
1 conflict

0x6d5d1fb5…86a7

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

1 conflict on slot 0x0d54fa3e81…1b3b3c

← previous block·next block →recent activity