← previous blocknext block →recent activity

Analyzing

Block #75,530,442

31 transactions · 23 stateful · 2026-05-19 03:19:55 UTC

Parallelism

81/100

Blocked

43%

Avg conflicts / tx

0.77

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,530,442  ·  31 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x69bca8d0…117b

0xd32edf…ff58

9 touches
10 conflicts

0x12bc0d2c…1c12

0x34b655…2a6f

6 touches
3 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

6 touches
3 conflicts

0x7c403af1…31b1

0x3bd359…433a

4 touches
1 conflict

0x50e10826…843b

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a2

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a4

0x8d66a4…3095

4 touches
1 conflict

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity