← previous blocknext block →recent activity

Analyzing

Block #74,766,883

20 transactions · 16 stateful · 2026-05-15 14:11:10 UTC

Parallelism

85/100

Blocked

56%

Avg conflicts / tx

0.6

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,766,883  ·  20 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

0x8a35acfb…d1a9

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1aa

0x8d66a4…3095

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x86f6085e…8da4

0xd32edf…ff58

5 touches
3 conflicts

0x17cd1479…00bb

0x8d66a4…3095

4 touches
1 conflict

0x74825c4e…32e9

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d19f

0x8d66a4…3095

4 touches
1 conflict

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: 0x8d66a43f…113095

3 conflicts on slot 0x8a35acfbc1…6bd1a9

← previous block·next block →recent activity