← previous blocknext block →recent activity

Analyzing

Block #93,665,390

18 transactions · 16 stateful · 2026-08-06 15:09:00 UTC

Parallelism

72/100

Blocked

50%

Avg conflicts / tx

0.89

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,665,390  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x99c5409a…25b7

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xfe5f6dff…8e9e

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xf4f9cac7…fd98

0x34b655…2a6f

6 touches
3 conflicts

0x590f63c9…5df9

0x34b655…2a6f

4 touches
1 conflict

0x80656e3b…9240

0x34b655…2a6f

4 touches
1 conflict

0x9eb101e5…003f

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

6 conflicts on slot 0x99c5409a28…0025b7

← previous block·next block →recent activity