← previous blocknext block →recent activity

Analyzing

Block #93,281,246

16 transactions · 15 stateful · 2026-08-05 06:57:46 UTC

Parallelism

81/100

Blocked

47%

Avg conflicts / tx

0.63

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #93,281,246  ·  16 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

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xd3b0a558…1513

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x9ff176a9…152e

0x065c9d…c394

4 touches
1 conflict

0x11258774…9892

0x2a68ba…90c5

4 touches
1 conflict

0x06e40499…165e

0x2b46c0…1669

4 touches
1 conflict

0xa605468c…1bfc

0x2b46c0…1669

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 0xca841faae5…71486a

← previous block·next block →recent activity