← previous blocknext block →recent activity

Analyzing

Block #93,306,793

20 transactions · 19 stateful · 2026-08-05 09:06:13 UTC

Parallelism

70/100

Blocked

47%

Avg conflicts / tx

1.05

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #93,306,793  ·  20 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

0xac2a0273…721b

0x34b655…2a6f

12 touches
15 conflicts

0x737acb78…fce8

0x34b655…2a6f

12 touches
15 conflicts

0x10f0a1bf…12c3

0x34b655…2a6f

6 touches
3 conflicts

0xa558e115…fc88

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xce06a0f7…efef

0x34b655…2a6f

5 touches
3 conflicts

0x6d1b72ee…6b78

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

15 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity