← previous blocknext block →recent activity

Analyzing

Block #93,926,831

23 transactions · 20 stateful · 2026-08-07 13:03:49 UTC

Parallelism

74/100

Blocked

40%

Avg conflicts / tx

0.61

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #93,926,831  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf7af6137…150c

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xfb24441a…4183

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc8c615d4…5da3

0x34b655…2a6f

4 touches
1 conflict

0x92b49f44…ee4f

0x34b655…2a6f

4 touches
1 conflict

0xa6464996…3af9

0x34b655…2a6f

4 touches
1 conflict

0xa80dcb46…ae9f

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 0xf7af613782…f0150c

← previous block·next block →recent activity