← previous blocknext block →recent activity

Analyzing

Block #94,969,470

26 transactions · 23 stateful · 2026-08-11 04:45:25 UTC

Parallelism

58/100

Blocked

65%

Avg conflicts / tx

1.73

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #94,969,470  ·  26 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x0a57a2b8…3cdd

0x34b655…2a6f

12 touches
15 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

10 touches
10 conflicts

0xec7d120d…7084

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x9d615dde…2d97

0x34b655…2a6f

6 touches
3 conflicts

0x1a5d321d…a474

0x34b655…2a6f

6 touches
3 conflicts

0xae28870c…072f

0x34b655…2a6f

6 touches
3 conflicts

0x8b501dcf…1040

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 0x0a57a2b8cd…773cdd

← previous block·next block →recent activity