← previous blocknext block →recent activity

Analyzing

Block #93,572,187

21 transactions · 20 stateful · 2026-08-06 07:20:27 UTC

Parallelism

67/100

Blocked

45%

Avg conflicts / tx

1.19

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #93,572,187  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0x99c5409a…25b7

0x34b655…2a6f

8 touches
6 conflicts

0x8218911e…3bed

0x34b655…2a6f

6 touches
3 conflicts

0x31644e15…5b87

0x34b655…2a6f

6 touches
3 conflicts

0x935a37fd…0514

0x34b655…2a6f

4 touches
1 conflict

0x939cdd56…00c8

0x34b655…2a6f

4 touches
1 conflict

0xa6f5b3f2…a865

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

21 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity