← previous blocknext block →recent activity

Analyzing

Block #73,991,646

6 transactions · 5 stateful · 2026-05-12 00:01:10 UTC

Parallelism

67/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,991,646  ·  6 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

0x7d190071…b2d4

0x188d58…ea8e

4 touches
1 conflict

0x4aade15f…3602

0x188d58…ea8e

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x036b6384…3db0

0x15c2c5…05e6

2 touches
0 conflicts

0x40e5ea25…2042

0x188d58…ea8e

2 touches
0 conflicts

0x838ab8c7…6be3

0x188d58…ea8e

2 touches
0 conflicts

0x838ab8c7…6be4

0x188d58…ea8e

2 touches
0 conflicts

0xe75ce681…ba5f

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 0x7d19007168…69b2d4

← previous block·next block →recent activity