← previous blocknext block →recent activity

Analyzing

Block #93,248,774

20 transactions · 18 stateful · 2026-08-05 04:14:30 UTC

Parallelism

60/100

Blocked

56%

Avg conflicts / tx

1.2

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #93,248,774  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

12 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0xa56e54d0…2d39

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xd5e06c4f…b14e

0x34b655…2a6f

6 touches
3 conflicts

0xea2d3331…6e34

0x1b6862…e19c

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

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

← previous block·next block →recent activity