← previous blocknext block →recent activity

Analyzing

Block #73,324,192

20 transactions · 16 stateful · 2026-05-08 21:41:37 UTC

Parallelism

70/100

Blocked

31%

Avg conflicts / tx

0.5

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,324,192  ·  20 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

0x8d0dfe2c…3345

0x2a68ba…90c5

8 touches
6 conflicts

0xd821ae10…fe17

0xc8689a…ee79

6 touches
3 conflicts

0x605dee99…e784

0x065c9d…c394

6 touches
3 conflicts

0xb1d0c4de…7372

0x065c9d…c394

6 touches
3 conflicts

0xde54a25e…1439

0x065c9d…c394

6 touches
3 conflicts

0xfc3cb767…518f

0x065c9d…c394

6 touches
3 conflicts

0x1a4b4152…0a08

0xaba216…a862

6 touches
3 conflicts

0x3e4b8d9f…b8a7

0xaba216…a862

6 touches
3 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: 0x2a68ba18…8e90c5

6 conflicts on slot 0x8d0dfe2c6c…173345

← previous block·next block →recent activity