← previous blocknext block →recent activity

Analyzing

Block #93,361,187

20 transactions · 19 stateful · 2026-08-05 13:39:42 UTC

Parallelism

75/100

Blocked

37%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #93,361,187  ·  20 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

0xac3e4969…39e9

0x34b655…2a6f

6 touches
3 conflicts

0x45ea7a97…bbb3

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xf9e23360…8ef7

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x34a1ee7e…fb20

0x34b655…2a6f

4 touches
1 conflict

0x3a0901d8…c944

0x34b655…2a6f

4 touches
1 conflict

0x4981d48d…e2ef

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 0xac3e4969cf…1739e9

← previous block·next block →recent activity