← previous blocknext block →recent activity

Analyzing

Block #73,693,450

20 transactions · 11 stateful · 2026-05-10 14:44:17 UTC

Parallelism

90/100

Blocked

27%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,693,450  ·  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

0xdd70bea3…1ffe

0x3bd359…433a

4 touches
1 conflict

0x3e733ae4…4598

0x34b655…2a6f

4 touches
1 conflict

0xaa8a1c54…ead3

0x34b655…2a6f

4 touches
1 conflict

0x375a9bf3…6910

0xd32edf…ff58

3 touches
1 conflict

0x1d7fda6d…fd1d

0x065c9d…c394

2 touches
0 conflicts

0x529acb6a…fcc6

0x065c9d…c394

2 touches
0 conflicts

0x00f7e3b7…e015

0x188d58…ea8e

2 touches
0 conflicts

0x00f7e3b7…e016

0x188d58…ea8e

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: 0x3bd359c1…15433a

1 conflict on slot 0xdd70bea3b0…701ffe

← previous block·next block →recent activity