← previous blocknext block →recent activity

Analyzing

Block #101,064,343

20 transactions · 19 stateful · 2026-09-01 14:20:01 UTC

Parallelism

85/100

Blocked

32%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #101,064,343  ·  20 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xbf3a793e…6f14

0x8964d7…10f8

4 touches
1 conflict

0x51fc8795…126f

0x34b655…2a6f

4 touches
1 conflict

0x68531239…e9a3

0x34b655…2a6f

4 touches
1 conflict

0xba5e7fa7…b319

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0xe8f860c0…35c9

0x34b655…2a6f

4 touches
1 conflict

0x177211e2…1c2d

0x754704…b603

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: 0x8964d7c9…5b10f8

1 conflict on slot 0xbf3a793e8e…c06f14

← previous block·next block →recent activity