← previous blocknext block →recent activity

Analyzing

Block #102,094,362

20 transactions · 19 stateful · 2026-09-05 04:50:14 UTC

Parallelism

65/100

Blocked

42%

Avg conflicts / tx

1.25

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #102,094,362  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x62bb20db…431e

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0x53e08444…d671

0x34b655…2a6f

6 touches
3 conflicts

0x55fc72dc…f3c5

0x34b655…2a6f

6 touches
3 conflicts

0x56e0d685…c960

0x34b655…2a6f

6 touches
3 conflicts

0x65f011a5…bc6e

0x34b655…2a6f

6 touches
3 conflicts

0x67043b0b…97d7

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

21 conflicts on slot 0x62bb20db5f…cb431e

← previous block·next block →recent activity