← previous blocknext block →recent activity

Analyzing

Block #74,498,632

15 transactions · 12 stateful · 2026-05-14 08:15:03 UTC

Parallelism

87/100

Blocked

17%

Avg conflicts / tx

0.27

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,498,632  ·  15 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

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xfc027d2d…4aa2

0x065c9d…c394

3 touches
1 conflict

0xfed40a77…e47f

0x065c9d…c394

3 touches
1 conflict

0x38ea16a2…3f3d

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0000

0x139aab…382b

2 touches
0 conflicts

0x00000000…0001

0x139aab…382b

2 touches
0 conflicts

0x00000000…0003

0x139aab…382b

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 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity