← previous blocknext block →recent activity

Analyzing

Block #94,808,126

26 transactions · 25 stateful · 2026-08-10 15:13:52 UTC

Parallelism

62/100

Blocked

56%

Avg conflicts / tx

1.81

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #94,808,126  ·  26 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

14 touches
21 conflicts

0xf5ea108a…dbf6

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…00c9

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x0a57a2b8…3cdd

0x34b655…2a6f

6 touches
3 conflicts

0xc6b9bb4b…145a

0x34b655…2a6f

6 touches
3 conflicts

0x856d2776…04c9

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

21 conflicts on slot 0xec7d120df9…5d7084

← previous block·next block →recent activity