← previous blocknext block →recent activity

Analyzing

Block #94,914,705

18 transactions · 16 stateful · 2026-08-11 00:09:58 UTC

Parallelism

83/100

Blocked

44%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #94,914,705  ·  18 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

0x00000000…0001

0xfa32f9…f3f0

6 touches
3 conflicts

0x679795a0…a28c

0xfa32f9…f3f0

6 touches
3 conflicts

0x99f666e3…b2a2

0x3bd359…433a

6 touches
3 conflicts

0x9194f4a3…10b8

0x754704…b603

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0000

0xfa32f9…f3f0

6 touches
3 conflicts

0x11b69a7e…334e

0x01bff4…1071

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: 0xfa32f9ec…fef3f0

3 conflicts on slot 0x0000000000…000001

← previous block·next block →recent activity