← previous blocknext block →recent activity

Analyzing

Block #74,526,902

18 transactions · 15 stateful · 2026-05-14 11:25:20 UTC

Parallelism

78/100

Blocked

27%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,526,902  ·  18 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

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xc6a8c250…737e

0x1b6862…e19c

4 touches
1 conflict

0xe91d055f…d8a9

0xd32edf…ff58

3 touches
1 conflict

0x801d6be2…acd8

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: 0x754704bc…afb603

3 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity