← previous blocknext block →recent activity

Analyzing

Block #94,811,395

21 transactions · 19 stateful · 2026-08-10 15:30:19 UTC

Parallelism

62/100

Blocked

53%

Avg conflicts / tx

1.33

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #94,811,395  ·  21 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

0xa3a621f8…75a2

0x34b655…2a6f

12 touches
15 conflicts

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0x251e4ed8…a3f4

0x34b655…2a6f

4 touches
1 conflict

0x33c49d59…9997

0x34b655…2a6f

4 touches
1 conflict

0x4327afd2…1b3a

0x34b655…2a6f

4 touches
1 conflict

0x48a0f121…953b

0x34b655…2a6f

4 touches
1 conflict

0x539ac47f…eb6f

0x34b655…2a6f

4 touches
1 conflict

0x6b47245e…a342

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

15 conflicts on slot 0xa3a621f8f3…6975a2

← previous block·next block →recent activity