← previous blocknext block →recent activity

Analyzing

Block #74,606,211

16 transactions · 13 stateful · 2026-05-14 20:18:47 UTC

Parallelism

88/100

Blocked

15%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,606,211  ·  16 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

0xeeb8b7fc…24d6

0x6657d1…8ccc

4 touches
1 conflict

0x3923d7de…bb41

0x754704…b603

4 touches
1 conflict

0x81955a0a…29ee

0x6657d1…8ccc

4 touches
1 conflict

0x9aa860ea…db2a

0xd32edf…ff58

3 touches
1 conflict

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0x14b833b1…22ec

0x065c9d…c394

2 touches
0 conflicts

0xbbee74c2…567a

0x065c9d…c394

2 touches
0 conflicts

0x46cb45de…a566

0x188d58…ea8e

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: 0x6657d192…be8ccc

1 conflict on slot 0xeeb8b7fc09…5d24d6

← previous block·next block →recent activity