← previous blocknext block →recent activity

Analyzing

Block #73,343,396

12 transactions · 11 stateful · 2026-05-08 23:49:18 UTC

Parallelism

83/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,343,396  ·  12 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

0x95e1330b…aa5b

0x065c9d…c394

4 touches
1 conflict

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x3caf2f7b…2df6

0x065c9d…c394

3 touches
1 conflict

0x83c1906a…29f8

0x065c9d…c394

2 touches
0 conflicts

0x92868cdd…9875

0x065c9d…c394

2 touches
0 conflicts

0xf817a951…2670

0x065c9d…c394

2 touches
0 conflicts

0xbdff944d…447e

0x2a68ba…90c5

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 0x95e1330b01…ceaa5b

← previous block·next block →recent activity