← previous blocknext block →recent activity

Analyzing

Block #74,218,462

22 transactions · 16 stateful · 2026-05-13 01:11:10 UTC

Parallelism

86/100

Blocked

19%

Avg conflicts / tx

0.14

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,218,462  ·  22 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x2b9c6652…d14e

0x754704…b603

4 touches
1 conflict

0x38bf360d…8c18

0xd32edf…ff58

3 touches
1 conflict

0x2d0b4438…745c

0x065c9d…c394

2 touches
0 conflicts

0x3656ae69…2fcd

0x065c9d…c394

2 touches
0 conflicts

0x4a8dcbfc…8cfc

0x065c9d…c394

2 touches
0 conflicts

0x587b1e5a…7184

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 0xdd70bea3b0…701ffe

← previous block·next block →recent activity