← previous blocknext block →recent activity

Analyzing

Block #73,343,740

35 transactions · 28 stateful · 2026-05-08 23:51:35 UTC

Parallelism

89/100

Blocked

46%

Avg conflicts / tx

0.66

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,343,740  ·  35 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 conflicts

0x1c354dc0…96de

0x754704…b603

8 touches
6 conflicts

0xf91b744e…9117

0x754704…b603

8 touches
6 conflicts

0xe501a8b4…1f58

0xd32edf…ff58

7 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x00000000…0003

0x63e48b…53f2

4 touches
1 conflict

0x00000000…0004

0x63e48b…53f2

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: 0x3bd359c1…15433a

6 conflicts on slot 0x6af306bb1d…092e81

← previous block·next block →recent activity