← previous blocknext block →recent activity

Analyzing

Block #93,555,370

18 transactions · 17 stateful · 2026-08-06 05:55:55 UTC

Parallelism

89/100

Blocked

12%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #93,555,370  ·  18 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x4e8c4408…d37b

0x34b655…2a6f

4 touches
1 conflict

0xa9a28cae…0bf3

0x34b655…2a6f

4 touches
1 conflict

0x002fed35…79fa

0x2a68ba…90c5

4 touches
1 conflict

0x4e8c4408…d37a

0x34b655…2a6f

4 touches
1 conflict

0x03083ef6…08aa

0x34b655…2a6f

2 touches
0 conflicts

0x34a1ee7e…fb20

0x34b655…2a6f

2 touches
0 conflicts

0x4bc1b6fd…ce27

0x34b655…2a6f

2 touches
0 conflicts

0x7fb99184…e8bb

0x34b655…2a6f

2 touches
0 conflicts

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

1 conflict on slot 0x4e8c4408ae…50d37b

← previous block·next block →recent activity