← previous blocknext block →recent activity

Analyzing

Block #93,657,860

24 transactions · 21 stateful · 2026-08-06 14:31:09 UTC

Parallelism

75/100

Blocked

38%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #93,657,860  ·  24 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

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0xbde524f4…43bf

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x37c0660b…e0bf

0x34b655…2a6f

7 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xce06a0f7…efef

0x34b655…2a6f

5 touches
3 conflicts

0xa1749bea…3a58

0x34b655…2a6f

4 touches
1 conflict

0xb1b58b33…874f

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 0x737acb7813…fafce8

← previous block·next block →recent activity