← previous blocknext block →recent activity

Analyzing

Block #73,964,741

10 transactions · 9 stateful · 2026-05-11 21:00:31 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,964,741  ·  10 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

0xae3fbd28…a18c

0x3bd359…433a

4 touches
1 conflict

0xbc467e7a…af36

0x21e325…7777

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x5bfd2e59…4fde

0x065c9d…c394

2 touches
0 conflicts

0x933a5607…5510

0x065c9d…c394

2 touches
0 conflicts

0x93e9b62e…a6c1

0x065c9d…c394

2 touches
0 conflicts

0xcc2c9778…2173

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

1 conflict on slot 0xae3fbd28fa…e7a18c

← previous block·next block →recent activity