← previous blocknext block →recent activity

Analyzing

Block #102,068,188

16 transactions · 16 stateful · 2026-09-05 02:37:26 UTC

Parallelism

50/100

Blocked

56%

Avg conflicts / tx

1.38

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #102,068,188  ·  16 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xf2b5d827…d865

0x34b655…2a6f

8 touches
6 conflicts

0xfc24540b…6463

0x34b655…2a6f

6 touches
3 conflicts

0x2c539d94…b63a

0x34b655…2a6f

6 touches
3 conflicts

0x64275949…d698

0x34b655…2a6f

6 touches
3 conflicts

0x8590b692…b267

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity