← previous blocknext block →recent activity

Analyzing

Block #73,655,164

14 transactions · 13 stateful · 2026-05-10 10:25:59 UTC

Parallelism

71/100

Blocked

23%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,655,164  ·  14 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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0xcb28b02b…8e4f

0x065c9d…c394

4 touches
1 conflict

0x8a05c648…7afb

0x065c9d…c394

3 touches
1 conflict

0x98b8a28d…d40d

0x065c9d…c394

3 touches
1 conflict

0x462c8be7…4f83

0x8d66a4…3095

2 touches
0 conflicts

0x5ba51e87…44ee

0x8d66a4…3095

2 touches
0 conflicts

0x8a35acfb…d1a7

0x8d66a4…3095

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity