← previous blocknext block →recent activity

Analyzing

Block #73,696,316

21 transactions · 18 stateful · 2026-05-10 15:03:35 UTC

Parallelism

62/100

Blocked

50%

Avg conflicts / tx

0.81

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,696,316  ·  21 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1ab

0x8d66a4…3095

6 touches
3 conflicts

0x7ee110ef…8394

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xe96c91d2…32ff

0x8d66a4…3095

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x143dba04…1b98

0x8d66a4…3095

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity