← previous blocknext block →recent activity

Analyzing

Block #73,986,943

15 transactions · 13 stateful · 2026-05-11 23:29:23 UTC

Parallelism

80/100

Blocked

31%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,986,943  ·  15 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

0x4d1acd7c…f345

0x5e1b1a…7777

4 touches
1 conflict

0x00000000…0001

0x75c3ab…4f0d

4 touches
1 conflict

0x00000000…0000

0x75c3ab…4f0d

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x88362ba4…377f

0x065c9d…c394

4 touches
1 conflict

0xd705a35d…c6c2

0x065c9d…c394

4 touches
1 conflict

0xf537eaa0…73c8

0x065c9d…c394

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: 0x5e1b1a14…587777

1 conflict on slot 0x4d1acd7cf0…b2f345

← previous block·next block →recent activity