← previous blocknext block →recent activity

Analyzing

Block #93,357,509

23 transactions · 21 stateful · 2026-08-05 13:21:12 UTC

Parallelism

61/100

Blocked

48%

Avg conflicts / tx

1

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #93,357,509  ·  23 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0xf3d10975…0d07

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x4bc1abab…5874

0x34b655…2a6f

5 touches
3 conflicts

0xb15c58ec…bd83

0x34b655…2a6f

4 touches
1 conflict

0xb2699a97…9c44

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 0xea02471df2…601542

← previous block·next block →recent activity