← previous blocknext block →recent activity

Analyzing

Block #94,810,618

22 transactions · 21 stateful · 2026-08-10 15:26:25 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.77

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #94,810,618  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xec7d120d…7084

0x34b655…2a6f

6 touches
3 conflicts

0x4acbdbcf…a8c6

0x34b655…2a6f

6 touches
3 conflicts

0x734ee320…caae

0x34b655…2a6f

6 touches
3 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

6 touches
3 conflicts

0x772ab420…c2f6

0x34b655…2a6f

4 touches
1 conflict

0x840d3ab7…c8c4

0x34b655…2a6f

4 touches
1 conflict

0xb01fbce1…3de6

0x34b655…2a6f

4 touches
1 conflict

0x10efb0c1…2ddc

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 0xec7d120df9…5d7084

← previous block·next block →recent activity