← previous blocknext block →recent activity

Analyzing

Block #102,064,388

25 transactions · 25 stateful · 2026-09-05 02:18:05 UTC

Parallelism

64/100

Blocked

36%

Avg conflicts / tx

1.08

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #102,064,388  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

14 touches
21 conflicts

0xbc8fb280…76a3

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x6fbc2e5a…e69c

0x34b655…2a6f

4 touches
1 conflict

0x7dd96c96…7335

0x34b655…2a6f

4 touches
1 conflict

0xb75367ff…a2b7

0x34b655…2a6f

4 touches
1 conflict

0x1a4b4833…cf01

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity