← previous blocknext block →recent activity

Analyzing

Block #73,273,862

15 transactions · 11 stateful · 2026-05-08 16:06:40 UTC

Parallelism

80/100

Blocked

36%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,273,862  ·  15 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xbd7e37a9…9eb5

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xea96ce3f…a965

0x065c9d…c394

4 touches
1 conflict

0xadbcbc65…8e8f

0x065c9d…c394

3 touches
1 conflict

0x7306f688…48f3

0x065c9d…c394

3 touches
1 conflict

0x67f2fb4c…cb20

0x065c9d…c394

2 touches
0 conflicts

0xdbcf78ea…cc69

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

3 conflicts on slot 0xbd7e37a9b5…859eb5

← previous block·next block →recent activity