← previous blocknext block →recent activity

Analyzing

Block #93,473,643

16 transactions · 14 stateful · 2026-08-05 23:05:05 UTC

Parallelism

88/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #93,473,643  ·  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

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0110331c…b891

0x34b655…2a6f

4 touches
1 conflict

0xbb38a037…5349

0x34b655…2a6f

4 touches
1 conflict

0xa169711f…c7f3

0x34b655…2a6f

4 touches
1 conflict

0xba228f10…2593

0x34b655…2a6f

4 touches
1 conflict

0x3f6855e6…2885

0x34b655…2a6f

3 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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity