← previous blocknext block →recent activity

Analyzing

Block #73,689,118

20 transactions · 15 stateful · 2026-05-10 14:15:07 UTC

Parallelism

80/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,689,118  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x711f6a23…b1bd

0xd32edf…ff58

7 touches
6 conflicts

0xdb95e18e…c73b

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0001

0x75c3ab…4f0d

4 touches
1 conflict

0x44ad89ba…cf83

0x5e1b1a…7777

4 touches
1 conflict

0x4d1acd7c…f345

0x5e1b1a…7777

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: 0xd32edf66…9fff58

6 conflicts on slot 0x711f6a2333…f8b1bd

← previous block·next block →recent activity