← previous blocknext block →recent activity

Analyzing

Block #73,016,060

16 transactions · 15 stateful · 2026-05-07 11:31:23 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1.13

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,016,060  ·  16 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x5d32a251…d929

0x34b655…2a6f

6 touches
3 conflicts

0x503ee695…ff73

0x065c9d…c394

4 touches
1 conflict

0x60904986…e706

0x065c9d…c394

4 touches
1 conflict

0x8aa53fbc…89a1

0x065c9d…c394

4 touches
1 conflict

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0xc6cfe829…fd9d

0x065c9d…c394

4 touches
1 conflict

0xc9f3da1a…8a9b

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity