← previous blocknext block →recent activity

Analyzing

Block #94,808,963

21 transactions · 19 stateful · 2026-08-10 15:18:05 UTC

Parallelism

86/100

Blocked

26%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #94,808,963  ·  21 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…0002

0xeae24c…0be0

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xac8a5059…fd42

0x34b655…2a6f

4 touches
1 conflict

0xad95efd9…b4cf

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf5ea108a…dbf6

0x34b655…2a6f

4 touches
1 conflict

0x0a57a2b8…3cdd

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: 0xeae24c72…e30be0

1 conflict on slot 0x0000000000…000002

← previous block·next block →recent activity