← previous blocknext block →recent activity

Analyzing

Block #74,766,916

13 transactions · 10 stateful · 2026-05-15 14:11:24 UTC

Parallelism

77/100

Blocked

30%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,766,916  ·  13 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

0xb9868b52…c77f

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x01737532…9b12

0x34b655…2a6f

4 touches
1 conflict

0xaade01bf…75d2

0x065c9d…c394

3 touches
1 conflict

0x443a3e47…f4a4

0x065c9d…c394

2 touches
0 conflicts

0x69e20c9c…23d8

0x065c9d…c394

2 touches
0 conflicts

0xbfe3d887…654f

0x065c9d…c394

2 touches
0 conflicts

0xfcb7b8b2…ebb3

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

1 conflict on slot 0xb9868b5233…c6c77f

← previous block·next block →recent activity