← previous blocknext block →recent activity

Analyzing

Block #74,406,830

7 transactions · 6 stateful · 2026-05-13 22:04:10 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,406,830  ·  7 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

0xc53af6f0…50bd

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x220f4f84…15f8

0x34b655…2a6f

4 touches
1 conflict

0x01637d1b…23b5

0x2ab50b…5c41

2 touches
0 conflicts

0x01794968…19a7

0x2ab50b…5c41

2 touches
0 conflicts

0x0cb137ac…92ed

0x2ab50b…5c41

2 touches
0 conflicts

0x0dbc153f…25c5

0x2ab50b…5c41

2 touches
0 conflicts

0x150e8d80…39ed

0x2ab50b…5c41

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: 0x34b6552d…112a6f

1 conflict on slot 0xc53af6f06d…c550bd

← previous block·next block →recent activity