← previous blocknext block →recent activity

Analyzing

Block #93,350,293

25 transactions · 25 stateful · 2026-08-05 12:44:55 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

1.12

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #93,350,293  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xdba08802…6ba7

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0xb4e0a934…5fc7

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x6d1b72ee…6b78

0x34b655…2a6f

6 touches
3 conflicts

0x4b6153f1…7f26

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

21 conflicts on slot 0xdba08802ff…3e6ba7

← previous block·next block →recent activity