← previous blocknext block →recent activity

Analyzing

Block #73,187,786

10 transactions · 9 stateful · 2026-05-08 06:34:05 UTC

Parallelism

70/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,187,786  ·  10 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2b94b604…5a3e

0x065c9d…c394

4 touches
1 conflict

0xc70b6cda…0003

0x065c9d…c394

4 touches
1 conflict

0x47c3fcf5…f1b0

0x065c9d…c394

4 touches
1 conflict

0x2a354a63…0515

0x065c9d…c394

4 touches
1 conflict

0x09d9e023…9710

0x065c9d…c394

3 touches
1 conflict

0x4d2850e5…e306

0x065c9d…c394

3 touches
1 conflict

0x426febec…1077

0x065c9d…c394

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity