← previous blocknext block →recent activity

Analyzing

Block #93,484,572

22 transactions · 21 stateful · 2026-08-06 00:00:01 UTC

Parallelism

82/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #93,484,572  ·  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

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x34a1ee7e…fb20

0x34b655…2a6f

4 touches
1 conflict

0x4bc1abab…5874

0x34b655…2a6f

4 touches
1 conflict

0x52b477bc…7ccf

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x8743e1ba…8331

0x34b655…2a6f

4 touches
1 conflict

0xa6848351…2238

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity