← previous blocknext block →recent activity

Analyzing

Block #94,199,994

23 transactions · 18 stateful · 2026-08-08 12:01:03 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,199,994  ·  23 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

0x433b3e0c…8ae8

0x065c9d…c394

8 touches
6 conflicts

0x002fed35…79fa

0x2a68ba…90c5

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x7e0b7922…c351

0x754704…b603

4 touches
1 conflict

0x4cabb80a…46bf

0x34b655…2a6f

4 touches
1 conflict

0xa2478c84…6956

0x754704…b603

4 touches
1 conflict

0xf5f53dc0…e809

0xd32edf…ff58

3 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: Kuru Exchange: Market-MON/USDC

6 conflicts on slot 0x433b3e0ceb…638ae8

← previous block·next block →recent activity