← previous blocknext block →recent activity

Analyzing

Block #93,571,876

15 transactions · 14 stateful · 2026-08-06 07:18:54 UTC

Parallelism

80/100

Blocked

36%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #93,571,876  ·  15 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x33ecd98b…29cb

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4d5053d1…3b7d

0x34b655…2a6f

4 touches
1 conflict

0x5e782d17…5317

0x34b655…2a6f

4 touches
1 conflict

0x6636a104…d595

0x34b655…2a6f

4 touches
1 conflict

0x6c28863e…840e

0x34b655…2a6f

4 touches
1 conflict

0x753b2da4…7a6d

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

3 conflicts on slot 0x99c5409a28…0025b7

← previous block·next block →recent activity