← previous blocknext block →recent activity

Analyzing

Block #93,926,417

17 transactions · 17 stateful · 2026-08-07 13:01:44 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.71

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #93,926,417  ·  17 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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x50c0dd87…1128

0x34b655…2a6f

4 touches
1 conflict

0x9cc36ddc…f1a3

0x34b655…2a6f

4 touches
1 conflict

0xa86351b8…2c5a

0x34b655…2a6f

4 touches
1 conflict

0xef05b756…d18f

0x851145…3f07

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 0x482471adbb…39122f

← previous block·next block →recent activity