← previous blocknext block →recent activity

Analyzing

Block #73,688,791

14 transactions · 10 stateful · 2026-05-10 14:12:54 UTC

Parallelism

86/100

Blocked

20%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,688,791  ·  14 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

0x6b2a871b…c3bd

0x065c9d…c394

4 touches
1 conflict

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0x6d21c40a…4aa0

0x065c9d…c394

3 touches
1 conflict

0x6e156c2d…788f

0x065c9d…c394

3 touches
1 conflict

0x18aed20c…48f3

0x000000…012a

2 touches
0 conflicts

0x4245e4e8…096e

0x000000…012a

2 touches
0 conflicts

0x7b43f938…3650

0x000000…012a

2 touches
0 conflicts

0x4dd1db39…a994

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: 0x065c9d28…a9c394

1 conflict on slot 0x6b2a871bb5…a6c3bd

← previous block·next block →recent activity