← previous blocknext block →recent activity

Analyzing

Block #74,343,073

14 transactions · 12 stateful · 2026-05-13 14:59:50 UTC

Parallelism

79/100

Blocked

17%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,343,073  ·  14 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

0x5107a34c…3eb8

0x065c9d…c394

4 touches
1 conflict

0x1dda4742…54d4

0x065c9d…c394

3 touches
1 conflict

0xdd01b101…516e

0x065c9d…c394

3 touches
1 conflict

0x698fad49…0ac7

0x065c9d…c394

2 touches
0 conflicts

0x71b38ca1…1716

0x065c9d…c394

2 touches
0 conflicts

0x8085a40b…eb4f

0x065c9d…c394

2 touches
0 conflicts

0x98d06e02…40eb

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity