← previous blocknext block →recent activity

Analyzing

Block #74,344,557

17 transactions · 14 stateful · 2026-05-13 15:09:42 UTC

Parallelism

88/100

Blocked

7%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,344,557  ·  17 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

0xf06c2cf5…61bd

0x34b655…2a6f

4 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x10a54c5e…fc22

0x065c9d…c394

2 touches
0 conflicts

0xb376c62f…d4ec

0x065c9d…c394

2 touches
0 conflicts

0x262bb27b…6b2c

0x11ed3b…2c96

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: 0x34b6552d…112a6f

1 conflict on slot 0xf06c2cf5e4…3161bd

← previous block·next block →recent activity