← previous blocknext block →recent activity

Analyzing

Block #102,205,237

20 transactions · 15 stateful · 2026-09-05 14:12:17 UTC

Parallelism

85/100

Blocked

40%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,205,237  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0x0ec07cf7…c0c9

0x34b655…2a6f

4 touches
1 conflict

0x32e1d03e…68a7

0x34b655…2a6f

4 touches
1 conflict

0x4f3cc09a…2804

0x34b655…2a6f

4 touches
1 conflict

0x53c94695…e25d

0x34b655…2a6f

4 touches
1 conflict

0x53e08444…d671

0x34b655…2a6f

4 touches
1 conflict

0x5b0a0cc2…bafe

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity