← previous blocknext block →recent activity

Analyzing

Block #94,220,904

19 transactions · 17 stateful · 2026-08-08 13:46:55 UTC

Parallelism

84/100

Blocked

12%

Avg conflicts / tx

0.16

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #94,220,904  ·  19 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

0x747f609d…1555

0x34b655…2a6f

4 touches
1 conflict

0x2a296f2d…2630

0x34b655…2a6f

4 touches
1 conflict

0x8d4c0bb9…ccd3

0x34b655…2a6f

4 touches
1 conflict

0x9ae859db…2d84

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf2f4727d…cdb7

0x34b655…2a6f

4 touches
1 conflict

0x05b1b07a…7a99

0x34b655…2a6f

4 touches
1 conflict

0x2c539d94…b63a

0x34b655…2a6f

2 touches
0 conflicts

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

1 conflict on slot 0x747f609d18…eb1555

← previous block·next block →recent activity