← previous blocknext block →recent activity

Analyzing

Block #74,420,752

17 transactions · 14 stateful · 2026-05-13 23:36:43 UTC

Parallelism

82/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,420,752  ·  17 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xfa2527aa…9dd5

0x34b655…2a6f

4 touches
1 conflict

0xaba8f143…aedc

0xd32edf…ff58

3 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

2 touches
0 conflicts

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x5138188e…796b

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity