← previous blocknext block →recent activity

Analyzing

Block #73,210,907

10 transactions · 10 stateful · 2026-05-08 09:07:55 UTC

Parallelism

40/100

Blocked

50%

Avg conflicts / tx

1.5

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,210,907  ·  10 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

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x7f189cf6…afab

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x28c912e9…fa01

0x065c9d…c394

4 touches
1 conflict

0x93c04212…a79c

0x065c9d…c394

4 touches
1 conflict

0xa008d370…48ba

0x065c9d…c394

3 touches
1 conflict

0x6979ec0e…e1c3

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

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity