← previous blocknext block →recent activity

Analyzing

Block #73,698,036

9 transactions · 8 stateful · 2026-05-10 15:15:12 UTC

Parallelism

78/100

Blocked

25%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,698,036  ·  9 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

0xb597f6af…64de

0x065c9d…c394

4 touches
1 conflict

0x1b9e654e…0a08

0x34b655…2a6f

4 touches
1 conflict

0x86ee6fff…aaad

0x065c9d…c394

3 touches
1 conflict

0xd34a6aeb…3940

0x065c9d…c394

3 touches
1 conflict

0x0ac31945…2c72

0x065c9d…c394

2 touches
0 conflicts

0x2177fbc7…acb3

0x065c9d…c394

2 touches
0 conflicts

0x529acb6a…fcc6

0x065c9d…c394

2 touches
0 conflicts

0x5a0326f5…8ce1

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 0xb597f6af71…bd64de

← previous block·next block →recent activity