← previous blocknext block →recent activity

Analyzing

Block #93,369,027

22 transactions · 19 stateful · 2026-08-05 14:19:07 UTC

Parallelism

77/100

Blocked

42%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,369,027  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0xb9834665…e363

0x34b655…2a6f

6 touches
3 conflicts

0x2697123c…8526

0x34b655…2a6f

4 touches
1 conflict

0x2d94ecd9…43db

0x34b655…2a6f

4 touches
1 conflict

0x34a1ee7e…fb20

0x34b655…2a6f

4 touches
1 conflict

0x34d95d94…3a16

0x34b655…2a6f

4 touches
1 conflict

0x3b5fbc7d…c8fe

0x34b655…2a6f

4 touches
1 conflict

0x58e9c5c4…c2a1

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

6 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity