← previous blocknext block →recent activity

Analyzing

Block #93,187,741

18 transactions · 17 stateful · 2026-08-04 23:07:39 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #93,187,741  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x5d46e6a0…5ed9

0x40c49f…2af0

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0x76d1e78d…7877

0x40c49f…2af0

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xb5a3b1be…8122

0x34b655…2a6f

4 touches
1 conflict

0x0226b774…a9ed

0x34b655…2a6f

4 touches
1 conflict

0x7ce5b49a…237c

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: 0x40c49f17…d22af0

3 conflicts on slot 0x5d46e6a0b6…d15ed9

← previous block·next block →recent activity