Block #73,176,419

← previous blocknext block →recent activity

Analyzing

Block #73,176,419

10 transactions · 10 stateful · 2026-05-08 05:18:16 UTC

Parallelism

80/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,176,419  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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…003d

0x065c9d…c394

4 touches
1 conflict

0x8a35acfb…d1aa

0x8d66a4…3095

4 touches
1 conflict

0x9d1bb389…c7d9

0x8d66a4…3095

4 touches
1 conflict

0x20342da1…81c0

0x065c9d…c394

2 touches
0 conflicts

0x3f7f7584…1934

0x065c9d…c394

2 touches
0 conflicts

0x43deeedb…9983

0x065c9d…c394

2 touches
0 conflicts

0x84ec5f2a…a3a4

0x065c9d…c394

2 touches
0 conflicts

0xba6c47e0…ec20

0x065c9d…c394

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: 0x065c9d28…a9c394

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity