← previous blocknext block →recent activity

Analyzing

Block #94,675,269

17 transactions · 15 stateful · 2026-08-10 04:04:08 UTC

Parallelism

53/100

Blocked

67%

Avg conflicts / tx

1.41

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #94,675,269  ·  17 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

10 touches
10 conflicts

0xf4f9cac7…fd98

0x34b655…2a6f

8 touches
6 conflicts

0x93b6fab0…09d6

0x34b655…2a6f

6 touches
3 conflicts

0x71ac6495…0817

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x97216283…fd1d

0x34b655…2a6f

4 touches
1 conflict

0x9927f045…9256

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

10 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity