← previous blocknext block →recent activity

Analyzing

Block #74,400,890

10 transactions · 8 stateful · 2026-05-13 21:24:36 UTC

Parallelism

70/100

Blocked

38%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,400,890  ·  10 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xbdf98ce2…9107

0x065c9d…c394

4 touches
1 conflict

0x44ad89ba…cf83

0x23c26b…7777

4 touches
1 conflict

0x81a7ba4d…8c4b

0x23c26b…7777

4 touches
1 conflict

0x00000000…0002

0xfdc9ea…8789

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0xfdc9ea…8789

4 touches
1 conflict

0x08fdca0b…4abf

0x3bd359…433a

4 touches
1 conflict

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity