← previous blocknext block →recent activity

Analyzing

Block #74,188,273

10 transactions · 7 stateful · 2026-05-12 21:50:20 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,188,273  ·  10 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

0xb6ed511f…6b68

0x34b655…2a6f

4 touches
1 conflict

0x37179c06…3c8c

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x00000000…000b

0x2a347b…e9d3

2 touches
0 conflicts

0x00000000…00c9

0x34b655…2a6f

2 touches
0 conflicts

0x499adbcf…eb20

0x34b655…2a6f

2 touches
0 conflicts

0x60a42a5e…9da2

0x34b655…2a6f

2 touches
0 conflicts

0x61ffa2a0…6ac4

0x34b655…2a6f

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 0xb6ed511f4c…ab6b68

← previous block·next block →recent activity