← previous blocknext block →recent activity

Analyzing

Block #93,555,806

16 transactions · 15 stateful · 2026-08-06 05:58:07 UTC

Parallelism

88/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #93,555,806  ·  16 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

0x7a606d8a…9700

0x34b655…2a6f

4 touches
1 conflict

0x8d5fc820…1750

0x34b655…2a6f

4 touches
1 conflict

0xcc6d0a0c…d380

0x34b655…2a6f

4 touches
1 conflict

0xf4c9a0df…dcd4

0x34b655…2a6f

4 touches
1 conflict

0xf4c9a0df…dcd5

0x34b655…2a6f

4 touches
1 conflict

0x002fed35…79fa

0x2a68ba…90c5

4 touches
1 conflict

0x5142c0df…970c

0x34b655…2a6f

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

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

1 conflict on slot 0x7a606d8a84…489700

← previous block·next block →recent activity