← previous blocknext block →recent activity

Analyzing

Block #101,801,439

21 transactions · 21 stateful · 2026-09-04 04:08:34 UTC

Parallelism

67/100

Blocked

48%

Avg conflicts / tx

1.24

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #101,801,439  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xca841faa…486a

0x34b655…2a6f

14 touches
21 conflicts

0xbc8fb280…76a3

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x55cde02d…89cb

0x34b655…2a6f

4 touches
1 conflict

0x7ea9d5d4…8219

0x34b655…2a6f

4 touches
1 conflict

0xb0f5d668…99ac

0x34b655…2a6f

4 touches
1 conflict

0xb3c96942…f0fc

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

21 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity