← previous blocknext block →recent activity

Analyzing

Block #74,476,115

13 transactions · 8 stateful · 2026-05-14 05:45:14 UTC

Parallelism

62/100

Blocked

50%

Avg conflicts / tx

0.77

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,476,115  ·  13 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x220f4f84…15f8

0x34b655…2a6f

4 touches
1 conflict

0xc53af6f0…50bd

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

2 touches
0 conflicts

0x37d49489…9309

0x34b655…2a6f

2 touches
0 conflicts

0x7170c140…36bc

0x34b655…2a6f

2 touches
0 conflicts

0x7b97d40a…09ed

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity