← previous blocknext block →recent activity

Analyzing

Block #94,809,258

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

Parallelism

74/100

Blocked

39%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #94,809,258  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x3ea25e92…a36d

0x34b655…2a6f

6 touches
3 conflicts

0x734ee320…caae

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x8b501dcf…1040

0x34b655…2a6f

4 touches
1 conflict

0x9aeab6b5…ad0f

0x34b655…2a6f

4 touches
1 conflict

0x9fbc6a76…9c29

0x34b655…2a6f

4 touches
1 conflict

0xa3a621f8…75a2

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity