← previous blocknext block →recent activity

Analyzing

Block #94,903,325

22 transactions · 17 stateful · 2026-08-10 23:12:44 UTC

Parallelism

82/100

Blocked

35%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,903,325  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x11b69a7e…334e

0x01bff4…1071

6 touches
3 conflicts

0x32626666…080c

0x34b655…2a6f

4 touches
1 conflict

0xbfb4b02a…4b47

0x34b655…2a6f

4 touches
1 conflict

0x595233b5…c4aa

0x754704…b603

4 touches
1 conflict

0x2ecf1f31…9a68

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

4 touches
1 conflict

0x00000000…004c

0x80c745…7210

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: USDC (USDC)

6 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity