← previous blocknext block →recent activity

Analyzing

Block #102,138,458

16 transactions · 15 stateful · 2026-09-05 08:33:44 UTC

Parallelism

88/100

Blocked

27%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #102,138,458  ·  16 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

0xd66696e0…0842

0x34b655…2a6f

4 touches
1 conflict

0xddf8f1be…65b5

0x34b655…2a6f

4 touches
1 conflict

0xe1c4e5ce…0dec

0x34b655…2a6f

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x2bb0d58d…9dcf

0x34b655…2a6f

4 touches
1 conflict

0x56a284d9…32e4

0x34b655…2a6f

4 touches
1 conflict

0x6974210b…154c

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 0xd66696e0dc…230842

← previous block·next block →recent activity