← previous blocknext block →recent activity

Analyzing

Block #102,053,971

20 transactions · 19 stateful · 2026-09-05 01:25:19 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

0.7

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,053,971  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

8 touches
6 conflicts

0x51fc8795…126f

0x34b655…2a6f

8 touches
6 conflicts

0x045532dd…4b7d

0x34b655…2a6f

4 touches
1 conflict

0xda18212c…b8b6

0x34b655…2a6f

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0xb0a7d979…59ac

0x34b655…2a6f

4 touches
1 conflict

0xb639a57c…a08a

0x34b655…2a6f

4 touches
1 conflict

0xb75367ff…a2b7

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

← previous block·next block →recent activity