← previous blocknext block →recent activity

Analyzing

Block #103,222,776

18 transactions · 17 stateful · 2026-09-09 03:52:52 UTC

Parallelism

89/100

Blocked

24%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #103,222,776  ·  18 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

0x044844a0…7418

0x34b655…2a6f

4 touches
1 conflict

0x045532dd…4b7d

0x34b655…2a6f

4 touches
1 conflict

0x0f13b598…f75b

0x34b655…2a6f

4 touches
1 conflict

0x0f763490…ff64

0x34b655…2a6f

4 touches
1 conflict

0x6ab7ec02…6741

0x34b655…2a6f

4 touches
1 conflict

0x7c68d10b…8386

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe7ad475a…0e41

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 0x044844a0f0…d07418

← previous block·next block →recent activity