← previous blocknext block →recent activity

Analyzing

Block #93,564,455

18 transactions · 16 stateful · 2026-08-06 06:41:35 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #93,564,455  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x34a1ee7e…fb20

0x34b655…2a6f

6 touches
3 conflicts

0x1e9a3afd…a6e5

0x34b655…2a6f

4 touches
1 conflict

0x237ae0f2…97d8

0x34b655…2a6f

4 touches
1 conflict

0x271d9d05…67de

0x34b655…2a6f

4 touches
1 conflict

0x33f54bd6…9ac3

0x34b655…2a6f

4 touches
1 conflict

0x408e66bb…3d6b

0x34b655…2a6f

4 touches
1 conflict

0x52fafa24…6bfa

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

← previous block·next block →recent activity