← previous blocknext block →recent activity

Analyzing

Block #73,706,362

15 transactions · 10 stateful · 2026-05-10 16:11:22 UTC

Parallelism

73/100

Blocked

30%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,706,362  ·  15 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0xa9988419…9f45

0x34b655…2a6f

2 touches
0 conflicts

0xac2a0273…7212

0x34b655…2a6f

2 touches
0 conflicts

0x99f666e3…b2a2

0x3bd359…433a

2 touches
0 conflicts

0x00000000…000b

0x754704…b603

2 touches
0 conflicts

0x2ad26e3d…5e47

0x754704…b603

2 touches
0 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: 0x065c9d28…a9c394

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity