← previous blocknext block →recent activity

Analyzing

Block #101,065,215

26 transactions · 23 stateful · 2026-09-01 14:24:26 UTC

Parallelism

77/100

Blocked

39%

Avg conflicts / tx

0.92

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #101,065,215  ·  26 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x68531239…e9a3

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x178fe051…465a

0x34b655…2a6f

4 touches
1 conflict

0x23529e13…6f25

0x34b655…2a6f

4 touches
1 conflict

0x4622b253…525e

0x34b655…2a6f

4 touches
1 conflict

0x63507b6e…8dc5

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

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

15 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity