← previous blocknext block →recent activity

Analyzing

Block #74,369,853

9 transactions · 8 stateful · 2026-05-13 17:57:55 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,369,853  ·  9 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

0xf9c274c6…41ed

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x75e131a8…f302

0x065c9d…c394

3 touches
1 conflict

0x61cb3937…e836

0x065c9d…c394

2 touches
0 conflicts

0x68851a97…aacb

0x065c9d…c394

2 touches
0 conflicts

0x7990ff96…a5bd

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0000

0x245374…e25c

2 touches
0 conflicts

0x046a928e…0012

0x2a68ba…90c5

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 0xf9c274c667…6841ed

← previous block·next block →recent activity