← previous blocknext block →recent activity

Analyzing

Block #101,324,341

14 transactions · 14 stateful · 2026-09-02 12:08:20 UTC

Parallelism

71/100

Blocked

57%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #101,324,341  ·  14 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

0x12e7c471…901c

0x34b655…2a6f

6 touches
3 conflicts

0xc446711e…b7cb

0x99c7a7…8bf0

4 touches
1 conflict

0xd1eae902…bfd4

0x754704…b603

4 touches
1 conflict

0x14b2b355…8ce5

0x99c7a7…8bf0

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x620a487a…622a

0x34b655…2a6f

4 touches
1 conflict

0x7e4873bc…5605

0x34b655…2a6f

4 touches
1 conflict

0xbc8fb280…76a3

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 0x12e7c471ad…22901c

← previous block·next block →recent activity