← previous blocknext block →recent activity

Analyzing

Block #73,343,751

36 transactions · 27 stateful · 2026-05-08 23:51:39 UTC

Parallelism

69/100

Blocked

63%

Avg conflicts / tx

1.89

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,343,751  ·  36 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xabb0859a…56fe

0xd32edf…ff58

21 touches
55 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x56a919c4…ab49

0xee8c0e…1242

6 touches
3 conflicts

0x00000000…0000

0xd5b70d…615b

6 touches
3 conflicts

0x00000000…0002

0xd5b70d…615b

6 touches
3 conflicts

0x00000000…0004

0xd5b70d…615b

6 touches
3 conflicts

0x18aed20c…48f3

0x000000…012a

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

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

55 conflicts on slot 0xabb0859a97…cf56fe

← previous block·next block →recent activity