← previous blocknext block →recent activity

Analyzing

Block #94,841,137

18 transactions · 17 stateful · 2026-08-10 17:59:57 UTC

Parallelism

56/100

Blocked

59%

Avg conflicts / tx

1.83

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #94,841,137  ·  18 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

0xc824469a…6425

0x34b655…2a6f

16 touches
28 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

12 touches
15 conflicts

0xb39cb1d8…effa

0x34b655…2a6f

10 touches
10 conflicts

0x0603347b…5872

0x34b655…2a6f

8 touches
6 conflicts

0xd7908b5f…56b9

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xf0a395cd…12ce

0x34b655…2a6f

6 touches
3 conflicts

0xd66696e0…0842

0x34b655…2a6f

6 touches
3 conflicts

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

28 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity