← previous blocknext block →recent activity

Analyzing

Block #101,308,229

20 transactions · 17 stateful · 2026-09-02 10:47:16 UTC

Parallelism

80/100

Blocked

47%

Avg conflicts / tx

0.7

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #101,308,229  ·  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

0x51fc8795…126f

0x34b655…2a6f

8 touches
6 conflicts

0xd17580f9…ece1

0x754704…b603

8 touches
6 conflicts

0x7dd96c96…7335

0x34b655…2a6f

6 touches
3 conflicts

0xb75367ff…a2b7

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x38d193c0…554e

0x34b655…2a6f

5 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x336486a4…20bd

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

6 conflicts on slot 0x51fc8795c8…57126f

← previous block·next block →recent activity