← previous blocknext block →recent activity

Analyzing

Block #74,643,944

12 transactions · 9 stateful · 2026-05-15 00:30:16 UTC

Parallelism

75/100

Blocked

22%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,643,944  ·  12 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

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x1a4c3394…bca1

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0xb29c4890…d50d

0x065c9d…c394

2 touches
0 conflicts

0xbd0d70ac…baff

0x065c9d…c394

2 touches
0 conflicts

0xefa07a26…7c5c

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x046a928e85…e50012

← previous block·next block →recent activity