← previous blocknext block →recent activity

Analyzing

Block #102,267,585

20 transactions · 19 stateful · 2026-09-05 19:28:08 UTC

Parallelism

70/100

Blocked

47%

Avg conflicts / tx

1.05

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,267,585  ·  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

0x51fc8795…126f

0x34b655…2a6f

12 touches
15 conflicts

0x29a58269…011a

0x34b655…2a6f

6 touches
3 conflicts

0x32e1d03e…68a7

0x34b655…2a6f

6 touches
3 conflicts

0xfd713bab…a651

0x34b655…2a6f

6 touches
3 conflicts

0x01315072…0e2d

0x34b655…2a6f

6 touches
3 conflicts

0x56e0d685…c960

0x34b655…2a6f

6 touches
3 conflicts

0x7dd96c96…7335

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

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

← previous block·next block →recent activity