← previous blocknext block →recent activity

Analyzing

Block #74,703,856

23 transactions · 17 stateful · 2026-05-15 07:10:00 UTC

Parallelism

65/100

Blocked

59%

Avg conflicts / tx

1.39

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,703,856  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x00000000…0002

0xab3526…fa38

16 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x81a7ba4d…8c4b

0x23c26b…7777

4 touches
1 conflict

0x00000000…0002

0xfdc9ea…8789

4 touches
1 conflict

0x44ad89ba…cf83

0x23c26b…7777

4 touches
1 conflict

0x8a85cf3d…2868

0x34b655…2a6f

4 touches
1 conflict

0x9dc9fa5f…7f23

0x34b655…2a6f

4 touches
1 conflict

0xfbbc35e2…f66b

0x34b655…2a6f

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: 0xab35264b…1cfa38

28 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity