← previous blocknext block →recent activity

Analyzing

Block #74,600,122

15 transactions · 13 stateful · 2026-05-14 19:37:51 UTC

Parallelism

80/100

Blocked

31%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,600,122  ·  15 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

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0xc17bf20f…8c64

0x065c9d…c394

4 touches
1 conflict

0x043ef7ad…1ef3

0x065c9d…c394

3 touches
1 conflict

0xa79117c4…5753

0x065c9d…c394

3 touches
1 conflict

0x80dc94b4…f3ef

0x065c9d…c394

2 touches
0 conflicts

0x848f34fb…9e03

0x065c9d…c394

2 touches
0 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

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: 0xab35264b…1cfa38

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity