← previous blocknext block →recent activity

Analyzing

Block #73,706,174

16 transactions · 14 stateful · 2026-05-10 16:10:07 UTC

Parallelism

88/100

Blocked

21%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,706,174  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x5d70606a…1d53

0x34b655…2a6f

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xeda2edc3…91d8

0x000000…012a

2 touches
0 conflicts

0x33018431…8f5c

0x188d58…ea8e

2 touches
0 conflicts

0x33018431…8f5d

0x188d58…ea8e

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: 0x188d586d…f9ea8e

1 conflict on slot 0x01e7b86585…4d6e6d

← previous block·next block →recent activity