← previous blocknext block →recent activity

Analyzing

Block #101,674,073

16 transactions · 14 stateful · 2026-09-03 17:27:57 UTC

Parallelism

69/100

Blocked

57%

Avg conflicts / tx

0.81

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #101,674,073  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

6 touches
3 conflicts

0x0965547c…bf94

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x635d0f25…4d22

0x34b655…2a6f

4 touches
1 conflict

0x6a9a9846…2636

0x34b655…2a6f

4 touches
1 conflict

0x6e7ff128…23b7

0x34b655…2a6f

4 touches
1 conflict

0x8d175439…fb79

0x34b655…2a6f

4 touches
1 conflict

0x96ed54e2…04ed

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 0xca841faae5…71486a

← previous block·next block →recent activity