← previous blocknext block →recent activity

Analyzing

Block #73,043,046

30 transactions · 20 stateful · 2026-05-07 14:31:01 UTC

Parallelism

87/100

Blocked

40%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,043,046  ·  30 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x3b8ffd61…f3ad

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xbb12db23…857e

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1539

0x34b655…2a6f

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x417d4db1…e923

0x34b655…2a6f

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: 0x34b6552d…112a6f

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity