← previous blocknext block →recent activity

Analyzing

Block #74,460,726

17 transactions · 9 stateful · 2026-05-14 04:02:55 UTC

Parallelism

88/100

Blocked

22%

Avg conflicts / tx

0.12

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,460,726  ·  17 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

0x578d9bc0…19c5

0x699abc…6a3b

4 touches
1 conflict

0xbe6a8ac2…88bd

0x699abc…6a3b

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x01a89030…f786

0x98dc6e…8633

2 touches
0 conflicts

0x0fc41e7b…6831

0x98dc6e…8633

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: 0x699abc15…c86a3b

1 conflict on slot 0x578d9bc0ef…b119c5

← previous block·next block →recent activity