← previous blocknext block →recent activity

Analyzing

Block #93,345,288

19 transactions · 18 stateful · 2026-08-05 12:19:45 UTC

Parallelism

58/100

Blocked

56%

Avg conflicts / tx

1.32

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #93,345,288  ·  19 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

0xa3a621f8…75a2

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xdfd68899…78e3

0x34b655…2a6f

6 touches
3 conflicts

0x8fe37a3f…4c89

0x34b655…2a6f

6 touches
3 conflicts

0xd29144b1…30b5

0x34b655…2a6f

6 touches
3 conflicts

0x2ee2ada1…4bee

0x34b655…2a6f

4 touches
1 conflict

0x42522e76…2592

0x34b655…2a6f

4 touches
1 conflict

0x42522e76…2593

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 0xa3a621f8f3…6975a2

← previous block·next block →recent activity