← previous blocknext block →recent activity

Analyzing

Block #74,655,197

13 transactions · 6 stateful · 2026-05-15 01:45:22 UTC

Parallelism

69/100

Blocked

50%

Avg conflicts / tx

0.31

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,655,197  ·  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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x29f8d809…61cc

0xd32edf…ff58

3 touches
1 conflict

0x7c67a870…729b

0x065c9d…c394

2 touches
0 conflicts

0x8916f1ee…78a0

0x065c9d…c394

2 touches
0 conflicts

0xbb2cfbfd…b5d8

0x065c9d…c394

2 touches
0 conflicts

0xbbee74c2…567a

0x065c9d…c394

2 touches
0 conflicts

0xcc692f30…a188

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