← previous blocknext block →recent activity

Analyzing

Block #101,839,178

24 transactions · 18 stateful · 2026-09-04 07:18:23 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #101,839,178  ·  24 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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x67c1f465…38b3

0x34b655…2a6f

4 touches
1 conflict

0xfcd5e68f…2a12

0x34b655…2a6f

4 touches
1 conflict

0x34b92204…abd4

0x34b655…2a6f

4 touches
1 conflict

0x53e08444…d671

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

6 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity