← previous blocknext block →recent activity

Analyzing

Block #102,216,212

20 transactions · 19 stateful · 2026-09-05 15:07:51 UTC

Parallelism

80/100

Blocked

32%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #102,216,212  ·  20 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

0x3774a68c…11ff

0x34b655…2a6f

6 touches
3 conflicts

0xd17580f9…ece1

0x754704…b603

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0x3b25d07f…1dee

0x34b655…2a6f

4 touches
1 conflict

0x1dc71894…1884

0x34b655…2a6f

4 touches
1 conflict

0x357fb47a…f9e0

0x34b655…2a6f

4 touches
1 conflict

0x9b28f8eb…778e

0x34b655…2a6f

4 touches
1 conflict

0xaf199a64…16ed

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 0x3774a68c81…7a11ff

← previous block·next block →recent activity