← previous blocknext block →recent activity

Analyzing

Block #73,673,692

13 transactions · 10 stateful · 2026-05-10 12:30:58 UTC

Parallelism

77/100

Blocked

30%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,673,692  ·  13 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

0x336c8edd…10a7

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x580c6fe7…0fe6

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

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

1 conflict on slot 0x336c8edd35…7d10a7

← previous block·next block →recent activity