← previous blocknext block →recent activity

Analyzing

Block #93,489,140

18 transactions · 16 stateful · 2026-08-06 00:22:59 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,489,140  ·  18 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

0x428b6e5b…8909

0x34b655…2a6f

6 touches
3 conflicts

0xd676e291…3ecf

0x34b655…2a6f

6 touches
3 conflicts

0xc6b9bb4b…145a

0x34b655…2a6f

6 touches
3 conflicts

0x1bf8d2af…d140

0x34b655…2a6f

6 touches
3 conflicts

0x4e8c4408…d37b

0x34b655…2a6f

4 touches
1 conflict

0x7b8f6ce5…a9aa

0x34b655…2a6f

4 touches
1 conflict

0x9ba6ae4a…90cb

0x34b655…2a6f

4 touches
1 conflict

0xa777fadb…7228

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 0x428b6e5b99…c18909

← previous block·next block →recent activity