← previous blocknext block →recent activity

Analyzing

Block #73,688,636

20 transactions · 16 stateful · 2026-05-10 14:11:51 UTC

Parallelism

90/100

Blocked

13%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,688,636  ·  20 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf2438038…5fa7

0x34b655…2a6f

4 touches
1 conflict

0x56480508…ac9c

0x065c9d…c394

2 touches
0 conflicts

0x8eb939b8…b274

0x065c9d…c394

2 touches
0 conflicts

0xa02f3c98…e0f3

0x065c9d…c394

2 touches
0 conflicts

0xa4995d24…b682

0x065c9d…c394

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity