← previous blocknext block →recent activity

Analyzing

Block #102,053,733

17 transactions · 15 stateful · 2026-09-05 01:24:07 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.59

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,053,733  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x19ab71d5…0015

0x34b655…2a6f

4 touches
1 conflict

0x6f232437…749d

0x34b655…2a6f

4 touches
1 conflict

0x97394169…cfc0

0x34b655…2a6f

4 touches
1 conflict

0xa4e9800f…4ab0

0x34b655…2a6f

4 touches
1 conflict

0xa57a72ed…64c2

0x34b655…2a6f

4 touches
1 conflict

0xbc8fb280…76a3

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity