← previous blocknext block →recent activity

Analyzing

Block #102,050,752

17 transactions · 15 stateful · 2026-09-05 01:09:02 UTC

Parallelism

82/100

Blocked

27%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,050,752  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x839c0c71…bada

0x34b655…2a6f

6 touches
3 conflicts

0x4a39a2a4…857b

0x34b655…2a6f

4 touches
1 conflict

0x4d7aaa4f…a8ec

0x34b655…2a6f

4 touches
1 conflict

0x939cdd56…00c8

0x34b655…2a6f

4 touches
1 conflict

0xaad800f2…8433

0x34b655…2a6f

4 touches
1 conflict

0xb91a6f59…722c

0x34b655…2a6f

4 touches
1 conflict

0x107b17c3…f6aa

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35d

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

3 conflicts on slot 0x839c0c712a…78bada

← previous block·next block →recent activity