← previous blocknext block →recent activity

Analyzing

Block #103,216,113

17 transactions · 15 stateful · 2026-09-09 03:19:17 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.59

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #103,216,113  ·  17 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

0x51fc8795…126f

0x34b655…2a6f

8 touches
6 conflicts

0x178fe051…465a

0x34b655…2a6f

4 touches
1 conflict

0x2186392b…f131

0x34b655…2a6f

4 touches
1 conflict

0x2c45dc1d…9eca

0x34b655…2a6f

4 touches
1 conflict

0x2f17174f…68b4

0x34b655…2a6f

4 touches
1 conflict

0x3a02129f…9eaf

0x34b655…2a6f

4 touches
1 conflict

0x448fdf2a…fab4

0x34b655…2a6f

4 touches
1 conflict

0x5f749304…d1c1

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

6 conflicts on slot 0x51fc8795c8…57126f

← previous block·next block →recent activity