← previous blocknext block →recent activity

Analyzing

Block #73,789,898

15 transactions · 13 stateful · 2026-05-11 01:35:11 UTC

Parallelism

60/100

Blocked

38%

Avg conflicts / tx

0.6

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,789,898  ·  15 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

8 touches
6 conflicts

0x3e733ae4…4598

0x34b655…2a6f

6 touches
3 conflicts

0x96504a63…52d2

0x8d66a4…3095

4 touches
1 conflict

0x6eba5e7f…4b52

0x34b655…2a6f

4 touches
1 conflict

0xa486f342…64d5

0x34b655…2a6f

4 touches
1 conflict

0x462c8be7…4f83

0x8d66a4…3095

4 touches
1 conflict

0x5ba51e87…44ee

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ac

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: 0x34b6552d…112a6f

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity