← previous blocknext block →recent activity

Analyzing

Block #74,331,192

24 transactions · 17 stateful · 2026-05-13 13:40:50 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.21

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,331,192  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xa94cf3f4…554c

0x8d66a4…3095

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xa10c86f8…4b74

0x3bd359…433a

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x7f430e47…4cbd

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a2

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a7

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

1 conflict on slot 0xa94cf3f4f8…4d554c

← previous block·next block →recent activity