← previous blocknext block →recent activity

Analyzing

Block #74,240,515

15 transactions · 11 stateful · 2026-05-13 03:37:46 UTC

Parallelism

87/100

Blocked

9%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,240,515  ·  15 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

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x0178c2de…b37d

0x8d66a4…3095

4 touches
1 conflict

0x74825c4e…32e9

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a9

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1aa

0x8d66a4…3095

4 touches
1 conflict

0x9345cae5…94a4

0x065c9d…c394

2 touches
0 conflicts

0xb3aa9412…3fb2

0x065c9d…c394

2 touches
0 conflicts

0xb56b9c07…0487

0x065c9d…c394

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

1 conflict on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity