← previous blocknext block →recent activity

Analyzing

Block #74,240,536

12 transactions · 8 stateful · 2026-05-13 03:37:54 UTC

Parallelism

83/100

Blocked

25%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,240,536  ·  12 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

0x768cffcd…2648

0x34b655…2a6f

4 touches
1 conflict

0x961973f5…4717

0x065c9d…c394

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

2 touches
0 conflicts

0xdcfea322…6ee8

0x065c9d…c394

2 touches
0 conflicts

0x064a3cb8…c43e

0x09475a…400f

2 touches
0 conflicts

0x13420bae…919f

0x09475a…400f

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 0x768cffcdb0…d12648

← previous block·next block →recent activity