← previous blocknext block →recent activity

Analyzing

Block #74,896,215

16 transactions · 13 stateful · 2026-05-16 04:34:06 UTC

Parallelism

81/100

Blocked

15%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,896,215  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x50e10826…843b

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1aa

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ab

0x8d66a4…3095

4 touches
1 conflict

0xc009105d…96f7

0x8d66a4…3095

4 touches
1 conflict

0x2b936aa5…05e2

0x141b1d…9583

2 touches
0 conflicts

0x2b936aa5…05e3

0x141b1d…9583

2 touches
0 conflicts

0x2b936aa5…05e5

0x141b1d…9583

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

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity