← previous blocknext block →recent activity

Analyzing

Block #93,363,838

28 transactions · 25 stateful · 2026-08-05 13:53:02 UTC

Parallelism

82/100

Blocked

28%

Avg conflicts / tx

0.54

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,363,838  ·  28 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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x3c3c85c0…2a46

0x34b655…2a6f

6 touches
3 conflicts

0x20492d53…80f9

0x34b655…2a6f

4 touches
1 conflict

0x2385516f…eca5

0x34b655…2a6f

4 touches
1 conflict

0x6c0e32fc…a6ca

0x34b655…2a6f

4 touches
1 conflict

0x758a0dd5…0f46

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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity