← previous blocknext block →recent activity

Analyzing

Block #74,427,333

6 transactions · 5 stateful · 2026-05-14 00:20:35 UTC

Parallelism

67/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,427,333  ·  6 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x68fbe281…c8fd

0x065c9d…c394

3 touches
1 conflict

0x846370b0…7f89

0x065c9d…c394

3 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

2 touches
0 conflicts

0x2b2c3c54…4a6d

0x065c9d…c394

2 touches
0 conflicts

0x36f6fac1…1548

0x065c9d…c394

2 touches
0 conflicts

0x68ecb5c4…a85c

0x065c9d…c394

2 touches
0 conflicts

0xd18e5b53…98c2

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity