← previous blocknext block →recent activity

Analyzing

Block #75,139,347

7 transactions · 7 stateful · 2026-05-17 07:38:14 UTC

Parallelism

43/100

Blocked

43%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,139,347  ·  7 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

0x8a35acfb…d1a6

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1a7

0x8d66a4…3095

6 touches
3 conflicts

0xfff38d9f…7063

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a0

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a2

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a5

0x8d66a4…3095

4 touches
1 conflict

0x9d1bb389…c7d9

0x8d66a4…3095

4 touches
1 conflict

0xc009105d…96f7

0x8d66a4…3095

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: 0x8d66a43f…113095

3 conflicts on slot 0x8a35acfbc1…6bd1a6

← previous block·next block →recent activity