← previous blocknext block →recent activity

Analyzing

Block #94,813,556

17 transactions · 16 stateful · 2026-08-10 15:41:12 UTC

Parallelism

76/100

Blocked

38%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,813,556  ·  17 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

0x30e49b8b…5fe9

0x34b655…2a6f

6 touches
3 conflicts

0x37bef14c…a6d5

0x34b655…2a6f

6 touches
3 conflicts

0xfd42a6b9…4c81

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x54526994…55b2

0x34b655…2a6f

4 touches
1 conflict

0x5d7e0e69…e6d2

0x34b655…2a6f

4 touches
1 conflict

0x92132ed7…2722

0x34b655…2a6f

4 touches
1 conflict

0xa3a621f8…75a2

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 0x30e49b8b07…ff5fe9

← previous block·next block →recent activity