← previous blocknext block →recent activity

Analyzing

Block #94,249,733

19 transactions · 17 stateful · 2026-08-08 16:13:15 UTC

Parallelism

84/100

Blocked

35%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #94,249,733  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x34a1ee7e…fb20

0x34b655…2a6f

6 touches
3 conflicts

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0xdbadf6b0…43b2

0x33176b…e078

4 touches
1 conflict

0xd9f1e40f…09a3

0x3bd359…433a

4 touches
1 conflict

0x527f20e3…82e7

0x754704…b603

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xaf90b3f4…5873

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

3 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity