← previous blocknext block →recent activity

Analyzing

Block #74,231,994

13 transactions · 11 stateful · 2026-05-13 02:41:06 UTC

Parallelism

69/100

Blocked

27%

Avg conflicts / tx

0.23

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,231,994  ·  13 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x6f3d3295…ac50

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x07982a87…3c23

0x065c9d…c394

3 touches
1 conflict

0x58256fd8…e1af

0x065c9d…c394

3 touches
1 conflict

0x11a73763…38ba

0xd32edf…ff58

3 touches
1 conflict

0xe5b4a16e…f69b

0x065c9d…c394

2 touches
0 conflicts

0xf823e97f…2ee6

0x065c9d…c394

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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 0x6f3d3295c1…74ac50

← previous block·next block →recent activity