← previous blocknext block →recent activity

Analyzing

Block #94,978,854

18 transactions · 18 stateful · 2026-08-11 05:32:37 UTC

Parallelism

78/100

Blocked

39%

Avg conflicts / tx

0.56

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #94,978,854  ·  18 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

0xf3d10975…0d07

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x3439dfbc…0d03

0x34b655…2a6f

6 touches
3 conflicts

0xc9327614…ba36

0x851145…3f07

4 touches
1 conflict

0x4e50038e…6e29

0x34b655…2a6f

4 touches
1 conflict

0x9adb2803…81f1

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

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

6 conflicts on slot 0xf3d10975b0…050d07

← previous block·next block →recent activity