← previous blocknext block →recent activity

Analyzing

Block #102,217,982

21 transactions · 19 stateful · 2026-09-05 15:16:46 UTC

Parallelism

81/100

Blocked

37%

Avg conflicts / tx

0.52

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,217,982  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xf139b130…d132

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0x5746581b…0cb1

0x34b655…2a6f

6 touches
3 conflicts

0x04d4f30d…4dfb

0x34b655…2a6f

4 touches
1 conflict

0x2ffcae11…8b17

0x34b655…2a6f

4 touches
1 conflict

0x3167d7d8…a06b

0x34b655…2a6f

4 touches
1 conflict

0x3774a68c…11ff

0x34b655…2a6f

4 touches
1 conflict

0x3b8a5029…dcdb

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 0xf139b130f5…fdd132

← previous block·next block →recent activity