← previous blocknext block →recent activity

Analyzing

Block #102,104,697

15 transactions · 15 stateful · 2026-09-05 05:42:39 UTC

Parallelism

67/100

Blocked

53%

Avg conflicts / tx

0.8

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,104,697  ·  15 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x51fc8795…126f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x045532dd…4b7d

0x34b655…2a6f

6 touches
3 conflicts

0x33b7fbba…64de

0x34b655…2a6f

4 touches
1 conflict

0x67c1f465…38b3

0x34b655…2a6f

4 touches
1 conflict

0x738d841d…3c29

0x34b655…2a6f

4 touches
1 conflict

0x76e02d19…7609

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 0x51fc8795c8…57126f

← previous block·next block →recent activity